Apparatus and method for transceiving broadcast signal

ABSTRACT

A method for transmitting a broadcast signal according to an embodiment of the present invention comprises generating service layer signaling information for discovery and acquisition of a broadcast service and a content component of the broadcast service; generating service list information including for service list building and discovery of the service layer signaling information; and physical layer processing of the service list information, service layer signaling information, and content component.

TECHNICAL FIELD

The present invention relates to an apparatus for transmitting abroadcast signal, an apparatus for receiving a broadcast signal andmethods for transmitting and receiving a broadcast signal.

BACKGROUND ART

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals arebeing developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

Technical Problem

A digital broadcast system can provide HD (high definition) images,multichannel audio and various additional services. However, datatransmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

Technical Solution

To solve the technical problem, a method and an apparatus fortransmitting a broadcast signal are disclosed.

A method for transmitting a broadcast signal including a contentcomponent of a broadcast service according to an embodiment of thepresent invention comprises generating service layer signalinginformation for discovery and acquisition of a broadcast service and acontent component of the broadcast service; generating service listinformation including for service list building and discovery of theservice layer signaling information; and physical layer processing ofthe service list information, service layer signaling information, andcontent component, wherein the service layer signaling information andthe content component may be transmitted by using at least one deliveryprotocol of the ROUTE (Real-Time Object Delivery over UnidirectionalTransport) protocol or MMT (MPEG Media Transport) protocol.

In a method for transmitting a broadcast signal according to anembodiment of the present invention, the service list information mayinclude first signaling information at a service list information leveland second signaling information at a service level. Also, the firstsignaling information may include capability information indicatingcapability required for processing of a broadcast service, broadcastsignaling location information including address information requiredfor acquiring service layer signaling information, and first URLsignaling information indicating a URL at which an ESG or a servicelayer signaling file for all of the services may be obtained; and thesecond signaling information may include second URL signalinginformation indicating a URL at which an ESG or a service layersignaling file for the corresponding service may be obtained.

Also, in a method for transmitting a broadcast signal according to anembodiment of the present invention, the capability information, thebroadcast signaling location information, and the first URL signalinginformation of the first signaling information; and the second URLsignaling information of the second signaling information may beincluded selectively in the service list information.

Also, the service list information may include service ID information of16-bit integer format for identifying the broadcast service, and theservice layer signaling information may include the service IDinformation and global service ID information of URI format foridentifying the broadcast service. Also, the global service ID may beincluded in an ESG transmitted over broadband.

Also, in a method for transmitting a broadcast signal according to anembodiment of the present invention, the service layer signalinginformation may be stored as a signaling template, and when a signalinginstance which changes the service signaling information is generated,transmitting the difference between the template and the signalinginstance as Diff information may be further included.

An apparatus for transmitting a broadcast signal according to anembodiment of the present invention may comprise a broadcast contentencoder processing a content component of a broadcast service; asignaling processor generating signaling information about a broadcastservice; and a physical layer processor performing physical layerprocessing on the content component and the signaling information,wherein the signaling information may include service layer signalinginformation for discovery and acquisition of the broadcast service andthe content component of the broadcast service; and service listinformation including information for service list building anddiscovery of the service layer signaling information; and the servicelayer signaling information and the content component may be transmittedby using at least one delivery protocol of the ROUTE (Real-Time ObjectDelivery over Unidirectional Transport) protocol or MMT (MPEG MediaTransport) protocol.

Advantageous Effects

The present invention can control quality of service (QoS) with respectto services or service components by processing data on the basis ofservice characteristics, thereby providing various broadcast services.

The present invention can achieve transmission flexibility bytransmitting various broadcast services through the same radio frequency(RF) signal bandwidth.

The present invention can provide methods and apparatuses fortransmitting and receiving broadcast signals, which enable digitalbroadcast signals to be received without error even when a mobilereception device is used or even in an indoor environment.

The present invention can effectively support future broadcast servicesin an environment supporting future hybrid broadcasting usingterrestrial broadcast networks and the Internet.

In what follows, additional effects of the present invention may bedescribed along with the description of the invention.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention;

FIG. 2 illustrates a relation between an SLT and service layer signaling(SLS) according to an embodiment of the present invention;

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention;

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention;

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention;

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention;

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention;

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention;

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention;

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention;

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention;

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention;

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side);

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention;

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention;

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention;

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides);

FIG. 18 is a block diagram illustrating a configuration of a broadcastsignal transmission apparatus for future broadcast services according toan embodiment of the present invention;

FIG. 19 is a block diagram illustrating a bit interleaved coding &modulation (BICM) block according to an embodiment of the presentinvention;

FIG. 20 is a block diagram illustrating a BICM block according toanother embodiment of the present invention;

FIG. 21 illustrates a bit interleaving process of physical layersignaling (PLS) according to an embodiment of the present invention;

FIG. 22 is a block diagram illustrating a configuration of a broadcastsignal reception apparatus for future broadcast services according to anembodiment of the present invention;

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention;

FIG. 24 is a table illustrating PLS1 data according to an embodiment ofthe present invention;

FIG. 25 is a table illustrating PLS2 data according to an embodiment ofthe present invention;

FIG. 26 is a table illustrating PLS2 data according to anotherembodiment of the present invention;

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention;

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention;

FIG. 29 illustrates time interleaving according to an embodiment of thepresent invention;

FIG. 30 illustrates a basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention;

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention;

FIG. 32 is a block diagram illustrating an interlaving address generatorincluding a main pseudo-random binary sequence (PRBS) generator and asub-PRBS generator according to each FFT mode according to an embodimentof the present invention;

FIG. 33 illustrates a main PRBS used for all FFT modes according to anembodiment of the present invention;

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleavingaddress for frequency interleaving according to an embodiment of thepresent invention;

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention;

FIG. 36 is a table illustrating an interleaving type applied accordingto the number of PLPs;

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver;

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver;

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver;

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver;

FIG. 41 is a receiver protocol stack according to an embodiment of thepresent invention.

FIG. 42 illustrates logical entities of service management, delivery,and physical layer and their relationship according to one embodiment ofthe present invention.

FIG. 43 illustrates a method for using service signaling forbootstrapping and service discovery according to an embodiment of thepresent invention.

FIG. 44 illustrates an FIT according to an embodiment of the presentinvention.

FIG. 45 an FIT descriptor according to an embodiment of the presentinvention.

FIG. 46 illustrates an embodiment of broadcastsignaling_location_descriptor( ).

FIG. 47 illustrates an embodiment of inet_signaling_location_descriptor().

FIG. 48 illustrates an embodiment of a query term wheninet_signaling_location_descriptor( ) is located at FIT level.

FIG. 49 illustrates an embodiment of a query term wheninet_signaling_location_descriptor( ) is located at service level.

FIG. 50 illustrates an XML format of the FIT shown and described inFIGS. 44 to 49.

FIG. 51 illustrates a service layer signaling data model according to anembodiment of the present invention.

FIG. 52 illustrates USBD according to one embodiment of the presentinvention.

FIG. 53 illustrates an S-TSID according to one embodiment of the presentinvention.

FIG. 54 illustrates hierarchical signaling architecture according to anembodiment of the present invention.

FIG. 55 illustrates a fast service scan signaling flow according to oneembodiment of the present invention.

FIG. 56 illustrates a full channel scan signaling flow according to anembodiment of the present invention.

FIG. 57 illustrates a service acquisition method in the pure broadcastaccording to an embodiment of the present invention.

FIG. 58 illustrates a service acquisition method in the pure broadcastaccording to an embodiment of the present invention.

FIG. 59 illustrates an ESG information acquisition method according toan embodiment of the present invention.

FIG. 60 illustrates a method for receiving a hybrid (multi-audiolanguage) service according to an embodiment of the present invention.

FIG. 61 illustrates a method for receiving a broadcast signal employinghandoff according to an embodiment of the present invention.

FIG. 62 illustrates a method for receiving a broadcast signal employingscalable coding according to an embodiment of the present invention.

FIG. 63 is an XML instance notation illustrating a method forencapsulating Diff in a metadataEnvelope element.

FIG. 64 illustrates a method for template pre-sharing and diff-patchingaccording to an embodiment of the present invention.

FIG. 65 illustrates an FIT delivery method according to an embodiment ofthe present invention.

FIG. 66 is a block diagram illustrating a hybrid broadcast receptionapparatus according to an embodiment of the present invention;

FIG. 67 is a block diagram illustrating a hybrid broadcast receiveraccording to an embodiment of the present invention;

FIG. 68 illustrates a protocol stack of a future hybrid broadcast systemaccording to an embodiment of the present invention;

FIG. 69 illustrates a structure of a transport frame delivered to aphysical layer of a future broadcast transmission system according to anembodiment of the present invention;

FIG. 70 illustrates a transport packet of an application layer transportprotocol according to an embodiment of the present invention;

FIG. 71 illustrates a method for transmitting signaling data by a futurebroadcast system according to an embodiment of the present invention;

FIG. 72 illustrates a syntax of a fast information table (FIT) accordingto an embodiment of the present invention.

FIG. 73 illustrates description about information included in the FITaccording to an embodiment of the present invention.

FIG. 74 illustrates a signaling connecting structure in a procedure inwhich a receiver acquires a service according to an embodiment of thepresent invention.

FIG. 75 illustrates a syntax of an FIT according to another embodimentof the present invention.

FIG. 76 is a table showing descriptor type and locations at whichdescriptors can be included according to an embodiment of the presentinvention.

FIG. 77 illustrates a signaling_broadcast_descriptor according to anembodiment of the present invention.

FIG. 78 illustrates meaning of a signaling_on_inet_descriptor (orsignaling_over_internet_descriptor) and values of inet_server_URL_typeinformation according to an embodiment of the present invention.

FIG. 79 illustrates meaning of a capability_descriptor and values ofcapability_category information according to an embodiment of thepresent invention.

FIG. 80 illustrates a syntax of an FIT according to another embodimentof the present invention.

FIG. 81 compares methods of signaling information about service levelsignaling transmitted through a broadcast network according to anembodiment of the present invention.

FIG. 82 is a table showing descriptor type and locations at whichdescriptors can be included according to an embodiment of the presentinvention.

FIG. 83 illustrates an FIT in XML format according to another embodimentof the present invention.

FIG. 84 illustrates description about information included in an FITaccording to an embodiment of the present invention.

FIG. 85 illustrates a signaling connecting structure in a procedure inwhich a receiver acquires a service according to an embodiment of thepresent invention.

FIG. 86 illustrates a signaling connecting structure in a procedure inwhich a receiver acquires a service according to another embodiment ofthe present invention.

FIG. 87 illustrates a template delivery table according to an embodimentof the present invention.

FIG. 88 illustrates a level descriptor according to an embodiment of thepresent invention.

FIG. 89 illustrates an FIT to which level descriptors are appliedaccording to an embodiment of the present invention.

FIG. 90 illustrates descriptors for the respective levels according toan embodiment of the present invention.

FIG. 91 illustrates an FIT to which level descriptors are appliedaccording to an embodiment of the present invention.

FIG. 92 illustrates a method for signaling a service ID according to anembodiment of the present invention.

FIG. 93 illustrates an embodiment of an ESG service fragment includingservice ID information of an FIT.

FIG. 94 illustrates a broadcast system structure according to anembodiment of the present invention.

FIG. 95 illustrates a method for transmitting a broadcast signalaccording to an embodiment of the present invention.

FIG. 96 illustrates a broadcast signal transmitter and a broadcastsignal receiver according to an embodiment of the present invention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although the terms used in the present invention are selected fromgenerally known and used terms, some of the terms mentioned in thedescription of the present invention have been selected by the applicantat his or her discretion, the detailed meanings of which are describedin relevant parts of the description herein. Furthermore, it is requiredthat the present invention is understood, not simply by the actual termsused but by the meanings of each term lying within.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, anultra high definition television (UHDTV) service, etc. The presentinvention may process broadcast signals for the future broadcastservices through non-MIMO (Multiple Input Multiple Output) or MIMOaccording to one embodiment. A non-MIMO scheme according to anembodiment of the present invention may include a MISO (Multiple InputSingle Output) scheme, a SISO (Single Input Single Output) scheme, etc.

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention.

Two schemes may be used in broadcast service delivery through abroadcast network.

In a first scheme, media processing units (MPUs) are transmitted usingan MMT protocol (MMTP) based on MPEG media transport (MMT). In a secondscheme, dynamic adaptive streaming over HTTP (DASH) segments may betransmitted using real time object delivery over unidirectionaltransport (ROUTE) based on MPEG DASH.

Non-timed content including NRT media, EPG data, and other files isdelivered with ROUTE. Signaling may be delivered over MMTP and/or ROUTE,while bootstrap signaling information is provided by the means of theService List Table (SLT).

In hybrid service delivery, MPEG DASH over HTTP/TCP/IP is used on thebroadband side. Media files in ISO Base Media File Format (BMFF) areused as the delivery, media encapsulation and synchronization format forboth broadcast and broadband delivery. Here, hybrid service delivery mayrefer to a case in which one or more program elements are deliveredthrough a broadband path.

Services are delivered using three functional layers. These are thephysical layer, the delivery layer and the service management layer. Thephysical layer provides the mechanism by which signaling, serviceannouncement and IP packet streams are transported over the broadcastphysical layer and/or broadband physical layer. The delivery layerprovides object and object flow transport functionality. It is enabledby the MMTP or the ROUTE protocol, operating on a UDP/IP multicast overthe broadcast physical layer, and enabled by the HTTP protocol on aTCP/IP unicast over the broadband physical layer. The service managementlayer enables any type of service, such as linear TV or HTML5application service, to be carried by the underlying delivery andphysical layers.

In this figure, a protocol stack part on a broadcast side may be dividedinto a part transmitted through the SLT and the MMTP, and a parttransmitted through ROUTE.

The SLT may be encapsulated through UDP and IP layers. Here, the SLTwill be described below. The MMTP may transmit data formatted in an MPUformat defined in MMT, and signaling information according to the MMTP.The data may be encapsulated through the UDP and IP layers. ROUTE maytransmit data formatted in a DASH segment form, signaling information,and non-timed data such as NRT data, etc. The data may be encapsulatedthrough the UDP and IP layers. According to a given embodiment, some orall processing according to the UDP and IP layers may be omitted. Here,the illustrated signaling information may be signaling informationrelated to a service.

The part transmitted through the SLT and the MMTP and the parttransmitted through ROUTE may be processed in the UDP and IP layers, andthen encapsulated again in a data link layer. The link layer will bedescribed below. Broadcast data processed in the link layer may bemulticast as a broadcast signal through processes such asencoding/interleaving, etc. in the physical layer.

In this figure, a protocol stack part on a broadband side may betransmitted through HTTP as described above. Data formatted in a DASHsegment form, signaling information, NRT information, etc. may betransmitted through HTTP. Here, the illustrated signaling informationmay be signaling information related to a service. The data may beprocessed through the TCP layer and the IP layer, and then encapsulatedinto the link layer. According to a given embodiment, some or all of theTCP, the IP, and the link layer may be omitted. Broadband data processedthereafter may be transmitted by unicast in the broadband through aprocess for transmission in the physical layer.

Service can be a collection of media components presented to the user inaggregate; components can be of multiple media types; a Service can beeither continuous or intermittent; a Service can be Real Time orNon-Real Time; Real Time Service can consist of a sequence of TVprograms.

FIG. 2 illustrates a relation between the SLT and SLS according to anembodiment of the present invention.

Service signaling provides service discovery and descriptioninformation, and comprises two functional components: Bootstrapsignaling via the Service List Table (SLT) and the Service LayerSignaling (SLS). These represent the information which is necessary todiscover and acquire user services. The SLT enables the receiver tobuild a basic service list, and bootstrap the discovery of the SLS foreach service.

The SLT can enable very rapid acquisition of basic service information.The SLS enables the receiver to discover and access services and theircontent components. Details of the SLT and SLS will be described below.

As described in the foregoing, the SLT may be transmitted throughUDP/IP. In this instance, according to a given embodiment, datacorresponding to the SLT may be delivered through the most robust schemein this transmission.

The SLT may have access information for accessing SLS delivered by theROUTE protocol. In other words, the SLT may be bootstrapped into SLSaccording to the ROUTE protocol. The SLS is signaling informationpositioned in an upper layer of ROUTE in the above-described protocolstack, and may be delivered through ROUTE/UDP/IP. The SLS may betransmitted through one of LCT sessions included in a ROUTE session. Itis possible to access a service component corresponding to a desiredservice using the SLS.

In addition, the SLT may have access information for accessing an MMTsignaling component delivered by MMTP. In other words, the SLT may bebootstrapped into SLS according to the MMTP. The SLS may be delivered byan MMTP signaling message defined in MMT. It is possible to access astreaming service component (MPU) corresponding to a desired serviceusing the SLS. As described in the foregoing, in the present invention,an NRT service component is delivered through the ROUTE protocol, andthe SLS according to the MMTP may include information for accessing theROUTE protocol. In broadband delivery, the SLS is carried overHTTP(S)/TCP/IP.

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention.

First, a description will be given of a relation among respectivelogical entities of service management, delivery, and a physical layer.

Services may be signaled as being one of two basic types. First type isa linear audio/video or audio-only service that may have an app-basedenhancement. Second type is a service whose presentation and compositionis controlled by a downloaded application that is executed uponacquisition of the service. The latter can be called an “app-based”service.

The rules regarding presence of ROUTE/LCT sessions and/or MMTP sessionsfor carrying the content components of a service may be as follows.

For broadcast delivery of a linear service without app-basedenhancement, the service's content components can be carried by either(but not both): (1) one or more ROUTE/LCT sessions, or (2) one or moreMMTP sessions.

For broadcast delivery of a linear service with app-based enhancement,the service's content components can be carried by: (1) one or moreROUTE/LCT sessions, and (2) zero or more MMTP sessions.

In certain embodiments, use of both MMTP and ROUTE for streaming mediacomponents in the same service may not be allowed.

For broadcast delivery of an app-based service, the service's contentcomponents can be carried by one or more ROUTE/LCT sessions.

Each ROUTE session comprises one or more LCT sessions which carry as awhole, or in part, the content components that make up the service. Instreaming services delivery, an LCT session may carry an individualcomponent of a user service such as an audio, video or closed captionstream. Streaming media is formatted as DASH Segments.

Each MMTP session comprises one or more MMTP packet flows which carryMMT signaling messages or as a whole, or in part, the content component.An MMTP packet flow may carry MMT signaling messages or componentsformatted as MPUs.

For the delivery of NRT User Services or system metadata, an LCT sessioncarries file-based content items. These content files may consist ofcontinuous (time-based) or discrete (non-time-based) media components ofan NRT service, or metadata such as Service Signaling or ESG fragments.Delivery of system metadata such as service signaling or ESG fragmentsmay also be achieved through the signaling message mode of MMTP.

A broadcast stream is the abstraction for an RF channel, which isdefined in terms of a carrier frequency centered within a specifiedbandwidth. It is identified by the pair [geographic area, frequency]. Aphysical layer pipe (PLP) corresponds to a portion of the RF channel.Each PLP has certain modulation and coding parameters. It is identifiedby a PLP identifier (PLPID), which is unique within the broadcast streamit belongs to. Here, PLP can be referred to as DP (data pipe).

Each service is identified by two forms of service identifier: a compactform that is used in the SLT and is unique only within the broadcastarea; and a globally unique form that is used in the SLS and the ESG. AROUTE session is identified by a source IP address, destination IPaddress and destination port number. An LCT session (associated with theservice component(s) it carries) is identified by a transport sessionidentifier (TSI) which is unique within the scope of the parent ROUTEsession. Properties common to the LCT sessions, and certain propertiesunique to individual LCT sessions, are given in a ROUTE signalingstructure called a service-based transport session instance description(S-TSID), which is part of the service layer signaling. Each LCT sessionis carried over a single physical layer pipe. According to a givenembodiment, one LCT session may be transmitted through a plurality ofPLPs. Different LCT sessions of a ROUTE session may or may not becontained in different physical layer pipes. Here, the ROUTE session maybe delivered through a plurality of PLPs. The properties described inthe S-TSID include the TSI value and PLPID for each LCT session,descriptors for the delivery objects/files, and application layer FECparameters.

A MMTP session is identified by destination IP address and destinationport number. An MMTP packet flow (associated with the servicecomponent(s) it carries) is identified by a packet_id which is uniquewithin the scope of the parent MMTP session. Properties common to eachMMTP packet flow, and certain properties of MMTP packet flows, are givenin the SLT. Properties for each MMTP session are given by MMT signalingmessages, which may be carried within the MMTP session. Different MMTPpacket flows of a MMTP session may or may not be contained in differentphysical layer pipes. Here, the MMTP session may be delivered through aplurality of PLPs. The properties described in the MMT signalingmessages include the packet_id value and PLPID for each MMTP packetflow. Here, the MMT signaling messages may have a form defined in MMT,or have a deformed form according to embodiments to be described below.

Hereinafter, a description will be given of low level signaling (LLS).

Signaling information which is carried in the payload of IP packets witha well-known address/port dedicated to this function is referred to aslow level signaling (LLS). The IP address and the port number may bedifferently configured depending on embodiments. In one embodiment, LLScan be transported in IP packets with address 224.0.23.60 anddestination port 4937/udp. LLS may be positioned in a portion expressedby “SLT” on the above-described protocol stack. However, according to agiven embodiment, the LLS may be transmitted through a separate physicalchannel (dedicated channel) in a signal frame without being subjected toprocessing of the UDP/IP layer.

UDP/IP packets that deliver LLS data may be formatted in a form referredto as an LLS table. A first byte of each UDP/IP packet that delivers theLLS data may correspond to a start of the LLS table. The maximum lengthof any LLS table is limited by the largest IP packet that can bedelivered from the PHY layer, 65,507 bytes.

The LLS table may include an LLS table ID field that identifies a typeof the LLS table, and an LLS table version field that identifies aversion of the LLS table. According to a value indicated by the LLStable ID field, the LLS table may include the above-described SLT or arating region table (RRT). The RRT may have information about contentadvisory rating.

Hereinafter, the SLT will be described. LLS can be signaling informationwhich supports rapid channel scans and bootstrapping of serviceacquisition by the receiver, and SLT can be a table of signalinginformation which is used to build a basic service listing and providebootstrap discovery of SLS.

The function of the SLT is similar to that of the program associationtable (PAT) in MPEG-2 Systems, and the fast information channel (FIC)found in ATSC Systems. For a receiver first encountering the broadcastemission, this is the place to start. SLT supports a rapid channel scanwhich allows a receiver to build a list of all the services it canreceive, with their channel name, channel number, etc., and SLT providesbootstrap information that allows a receiver to discover the SLS foreach service. For ROUTE/DASH-delivered services, the bootstrapinformation includes the destination IP address and destination port ofthe LCT session that carries the SLS. For MMT/MPU-delivered services,the bootstrap information includes the destination IP address anddestination port of the MMTP session carrying the SLS.

The SLT supports rapid channel scans and service acquisition byincluding the following information about each service in the broadcaststream. First, the SLT can include information necessary to allow thepresentation of a service list that is meaningful to viewers and thatcan support initial service selection via channel number or up/downselection. Second, the SLT can include information necessary to locatethe service layer signaling for each service listed. That is, the SLTmay include access information related to a location at which the SLS isdelivered.

The illustrated SLT according to the present embodiment is expressed asan XML document having an SLT root element. According to a givenembodiment, the SLT may be expressed in a binary format or an XMLdocument.

The SLT root element of the SLT illustrated in the figure may include@bsid, @sltSectionVersion, @sltSectionNumber, @totalSltSectionNumbers,@language, @capabilities, InetSigLoc and/or Service. According to agiven embodiment, the SLT root element may further include @providerId.According to a given embodiment, the SLT root element may not include@language.

The service element may include @serviceId, @SLTserviceSeqNumber,@protected, @majorChannelNo, @minorChannelNo, @serviceCategory,@shortServiceName, @hidden, @slsProtocolType, BroadcastSignaling,@slsPlpId, @slsDestinationIpAddress, @slsDestinationUdpPort,@slsSourceIpAddress, @slsMajorProtocolVersion, @SlsMinorProtocolVersion,@serviceLanguage, @broadbandAccessRequired, @capabilities and/orInetSigLoc.

According to a given embodiment, an attribute or an element of the SLTmay be added/changed/deleted. Each element included in the SLT mayadditionally have a separate attribute or element, and some attribute orelements according to the present embodiment may be omitted. Here, afield which is marked with @ may correspond to an attribute, and a fieldwhich is not marked with @ may correspond to an element.

@bsid is an identifier of the whole broadcast stream. The value of BSIDmay be unique on a regional level.

@providerId can be an index of broadcaster that is using part or all ofthis broadcast stream. This is an optional attribute. When it's notpresent, it means that this broadcast stream is being used by onebroadcaster. @providerId is not illustrated in the figure.

@sltSectionVersion can be a version number of the SLT section. ThesltSectionVersion can be incremented by 1 when a change in theinformation carried within the slt occurs. When it reaches maximumvalue, it wraps around to 0.

@sltSectionNumber can be the number, counting from 1, of this section ofthe SLT. In other words, @sltSectionNumber may correspond to a sectionnumber of the SLT section. When this field is not used,@sltSectionNumber may be set to a default value of 1.

@totalSltSectionNumbers can be the total number of sections (that is,the section with the highest sltSectionNumber) of the SLT of which thissection is part. sltSectionNumber and totalSltSectionNumbers togethercan be considered to indicate “Part M of N” of one portion of the SLTwhen it is sent in fragments. In other words, when the SLT istransmitted, transmission through fragmentation may be supported. Whenthis field is not used, @totalSltSectionNumbers may be set to a defaultvalue of 1. A case in which this field is not used may correspond to acase in which the SLT is not transmitted by being fragmented.

@language can indicate primary language of the services included in thissit instance. According to a given embodiment, a value of this field mayhave be a three-character language code defined in the ISO. This fieldmay be omitted.

@capabilities can indicate required capabilities for decoding andmeaningfully presenting the content for all the services in this sitinstance.

InetSigLoc can provide a URL telling the receiver where it can acquireany requested type of data from external server(s) via broadband. Thiselement may include @urlType as a lower field. According to a value ofthe @urlType field, a type of a URL provided by InetSigLoc may beindicated. According to a given embodiment, when the @urlType field hasa value of 0, InetSigLoc may provide a URL of a signaling server. Whenthe @urlType field has a value of 1, InetSigLoc may provide a URL of anESG server. When the @urlType field has other values, the field may bereserved for future use.

The service field is an element having information about each service,and may correspond to a service entry. Service element fieldscorresponding to the number of services indicated by the SLT may bepresent. Hereinafter, a description will be given of a lowerattribute/element of the service field.

@serviceId can be an integer number that uniquely identify this servicewithin the scope of this broadcast area. According to a givenembodiment, a scope of @serviceId may be changed. @SLTserviceSeqNumbercan be an integer number that indicates the sequence number of the SLTservice information with service ID equal to the serviceId attributeabove. SLTserviceSeqNumber value can start at 0 for each service and canbe incremented by 1 every time any attribute in this service element ischanged. If no attribute values are changed compared to the previousService element with a particular value of ServiceID thenSLTserviceSeqNumber would not be incremented. The SLTserviceSeqNumberfield wraps back to 0 after reaching the maximum value.

@protected is flag information which may indicate whether one or morecomponents for significant reproduction of the service are in aprotected state. When set to “1” (true), that one or more componentsnecessary for meaningful presentation is protected. When set to “0”(false), this flag indicates that no components necessary for meaningfulpresentation of the service are protected. Default value is false.

@majorChannelNo is an integer number representing the “major” channelnumber of the service. An example of the field may have a range of 1 to999.

@minorChannelNo is an integer number representing the “minor” channelnumber of the service. An example of the field may have a range of 1 to999.

@serviceCategory can indicate the category of this service. This fieldmay indicate a type that varies depending on embodiments. According to agiven embodiment, when this field has values of 1, 2, and 3, the valuesmay correspond to a linear A/V service, a linear audio only service, andan app-based service, respectively. When this field has a value of 0,the value may correspond to a service of an undefined category. Whenthis field has other values except for 1, 2, and 3, the field may bereserved for future use. @shortServiceName can be a short string name ofthe Service.

@hidden can be boolean value that when present and set to “true”indicates that the service is intended for testing or proprietary use,and is not to be selected by ordinary TV receivers. The default value is“false” when not present.

@slsProtocolType can be an attribute indicating the type of protocol ofService Layer Signaling used by this service. This field may indicate atype that varies depending on embodiments. According to a givenembodiment, when this field has values of 1 and 2, protocols of SLS usedby respective corresponding services may be ROUTE and MMTP,respectively. When this field has other values except for 0, the fieldmay be reserved for future use. This field may be referred to as@slsProtocol.

BroadcastSignaling and lower attributes/elements thereof may provideinformation related to broadcast signaling. When the BroadcastSignalingelement is not present, the child element InetSigLoc of the parentservice element can be present and its attribute urlType includesURL_type 0x00 (URL to signaling server). In this case attribute urlsupports the query parameter svc=<service_id> where service_idcorresponds to the serviceId attribute for the parent service element.

Alternatively when the BroadcastSignaling element is not present, theelement InetSigLoc can be present as a child element of the slt rootelement and the attribute urlType of that InetSigLoc element includesURL_type 0x00 (URL to signaling server). In this case, attribute url forURL_type 0x00 supports the query parameter svc=<service_id> whereservice id corresponds to the serviceId attribute for the parent Serviceelement.

@slsPlpId can be a string representing an integer number indicating thePLP ID of the physical layer pipe carrying the SLS for this service.

@slsDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying SLS data for this service.

@slsDestinationUdpPort can be a string containing the port number of thepackets carrying SLS data for this service. As described in theforegoing, SLS bootstrapping may be performed by destination IP/UDPinformation.

@slsSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying SLS data for this service.

@slsMajorProtocolVersion can be major version number of the protocolused to deliver the service layer signaling for this service. Defaultvalue is 1.

@SlsMinorProtocolVersion can be minor version number of the protocolused to deliver the service layer signaling for this service. Defaultvalue is 0.

@serviceLanguage can be a three-character language code indicating theprimary language of the service. A value of this field may have a formthat varies depending on embodiments.

@broadbandAccessRequired can be a Boolean indicating that broadbandaccess is required for a receiver to make a meaningful presentation ofthe service. Default value is false. When this field has a value ofTrue, the receiver needs to access a broadband for significant servicereproduction, which may correspond to a case of hybrid service delivery.

@capabilities can represent required capabilities for decoding andmeaningfully presenting the content for the service with service IDequal to the service Id attribute above.

InetSigLoc can provide a URL for access to signaling or announcementinformation via broadband, if available. Its data type can be anextension of the any URL data type, adding an @urlType attribute thatindicates what the URL gives access to. An @urlType field of this fieldmay indicate the same meaning as that of the @urlType field ofInetSigLoc described above. When an InetSigLoc element of attributeURL_type 0x00 is present as an element of the SLT, it can be used tomake HTTP requests for signaling metadata. The HTTP POST message bodymay include a service term. When the InetSigLoc element appears at thesection level, the service term is used to indicate the service to whichthe requested signaling metadata objects apply. If the service term isnot present, then the signaling metadata objects for all services in thesection are requested. When the InetSigLoc appears at the service level,then no service term is needed to designate the desired service. When anInetSigLoc element of attribute URL_type 0x01 is provided, it can beused to retrieve ESG data via broadband. If the element appears as achild element of the service element, then the URL can be used toretrieve ESG data for that service. If the element appears as a childelement of the SLT element, then the URL can be used to retrieve ESGdata for all services in that section.

In another example of the SLT, @sltSectionVersion, @sltSectionNumber,@totalSltSectionNumbers and/or @language fields of the SLT may beomitted

In addition, the above-described InetSigLoc field may be replaced by@sltInetSigUri and/or @sltInetEsgUri field. The two fields may includethe URI of the signaling server and URI information of the ESG server,respectively. The InetSigLoc field corresponding to a lower field of theSLT and the InetSigLoc field corresponding to a lower field of theservice field may be replaced in a similar manner.

The suggested default values may vary depending on embodiments. Anillustrated “use” column relates to the respective fields. Here, “1” mayindicate that a corresponding field is an essential field, and “0 . . .1” may indicate that a corresponding field is an optional field.

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention.

Hereinafter, SLS will be described.

SLS can be signaling which provides information for discovery andacquisition of services and their content components.

For ROUTE/DASH, the SLS for each service describes characteristics ofthe service, such as a list of its components and where to acquire them,and the receiver capabilities required to make a meaningful presentationof the service. In the ROUTE/DASH system, the SLS includes the userservice bundle description (USBD), the S-TSID and the DASH mediapresentation description (MPD). Here, USBD or user service description(USD) is one of SLS XML fragments, and may function as a signaling herbthat describes specific descriptive information. USBD/USD may beextended beyond 3GPP MBMS. Details of USBD/USD will be described below.

The service signaling focuses on basic attributes of the service itself,especially those attributes needed to acquire the service. Properties ofthe service and programming that are intended for viewers appear asservice announcement, or ESG data.

Having separate Service Signaling for each service permits a receiver toacquire the appropriate SLS for a service of interest without the needto parse the entire SLS carried within a broadcast stream.

For optional broadband delivery of Service Signaling, the SLT caninclude HTTP URLs where the Service Signaling files can be obtained, asdescribed above.

LLS is used for bootstrapping SLS acquisition, and subsequently, the SLSis used to acquire service components delivered on either ROUTE sessionsor MMTP sessions. The described figure illustrates the followingsignaling sequences. Receiver starts acquiring the SLT described above.Each service identified by service_id delivered over ROUTE sessionsprovides SLS bootstrapping information: PLPID(#1), source IP address(sIP1), destination IP address (dIP1), and destination port number(dPort1). Each service identified by service_id delivered over MMTPsessions provides SLS bootstrapping information: PLPID(#2), destinationIP address (dIP2), and destination port number (dPort2).

For streaming services delivery using ROUTE, the receiver can acquireSLS fragments carried over the IP/UDP/LCT session and PLP; whereas forstreaming services delivery using MMTP, the receiver can acquire SLSfragments carried over an MMTP session and PLP. For service deliveryusing ROUTE, these SLS fragments include USBD/USD fragments, S-TSIDfragments, and MPD fragments. They are relevant to one service. USBD/USDfragments describe service layer properties and provide URI referencesto S-TSID fragments and URI references to MPD fragments. In other words,the USBD/USD may refer to S-TSID and MPD. For service delivery usingMMTP, the USBD references the MMT signaling's MPT message, the MP Tableof which provides identification of package ID and location informationfor assets belonging to the service. Here, an asset is a multimedia dataentity, and may refer to a data entity which is combined into one uniqueID and is used to generate one multimedia presentation. The asset maycorrespond to a service component included in one service. The MPTmessage is a message having the MP table of MMT. Here, the MP table maybe an MMT package table having information about content and an MMTasset. Details may be similar to a definition in MMT. Here, mediapresentation may correspond to a collection of data that establishesbounded/unbounded presentation of media content.

The S-TSID fragment provides component acquisition informationassociated with one service and mapping between DASH Representationsfound in the MPD and in the TSI corresponding to the component of theservice. The S-TSID can provide component acquisition information in theform of a TSI and the associated DASH representation identifier, andPLPID carrying DASH segments associated with the DASH representation. Bythe PLPID and TSI values, the receiver collects the audio/videocomponents from the service and begins buffering DASH media segmentsthen applies the appropriate decoding processes.

For USBD listing service components delivered on MMTP sessions, asillustrated by “Service #2” in the described figure, the receiver alsoacquires an MPT message with matching MMT_package_id to complete theSLS. An MPT message provides the full list of service componentscomprising a service and the acquisition information for each component.Component acquisition information includes MMTP session information, thePLPID carrying the session and the packet_id within that session.

According to a given embodiment, for example, in ROUTE, two or moreS-TSID fragments may be used. Each fragment may provide accessinformation related to LCT sessions delivering content of each service.

In ROUTE, S-TSID, USBD/USD, MPD, or an LCT session delivering S-TSID,USBD/USD or MPD may be referred to as a service signaling channel. InMMTP, USBD/UD, an MMT signaling message, or a packet flow delivering theMMTP or USBD/UD may be referred to as a service signaling channel.

Unlike the illustrated example, one ROUTE or MMTP session may bedelivered through a plurality of PLPs. In other words, one service maybe delivered through one or more PLPs. As described in the foregoing,one LCT session may be delivered through one PLP. Unlike the figure,according to a given embodiment, components included in one service maybe delivered through different ROUTE sessions. In addition, according toa given embodiment, components included in one service may be deliveredthrough different MMTP sessions. According to a given embodiment,components included in one service may be delivered separately through aROUTE session and an MMTP session. Although not illustrated, componentsincluded in one service may be delivered via broadband (hybriddelivery).

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of SLS in delivery based onROUTE.

SLS provides detailed technical information to the receiver to enablethe discovery and access of services and their content components. Itcan include a set of XML-encoded metadata fragments carried over adedicated LCT session. That LCT session can be acquired using thebootstrap information contained in the SLT as described above. The SLSis defined on a per-service level, and it describes the characteristicsand access information of the service, such as a list of its contentcomponents and how to acquire them, and the receiver capabilitiesrequired to make a meaningful presentation of the service. In theROUTE/DASH system, for linear services delivery, the SLS consists of thefollowing metadata fragments: USBD, S-TSID and the DASH MPD. The SLSfragments can be delivered on a dedicated LCT transport session withTSI=0. According to a given embodiment, a TSI of a particular LCTsession (dedicated LCT session) in which an SLS fragment is deliveredmay have a different value. According to a given embodiment, an LCTsession in which an SLS fragment is delivered may be signaled using theSLT or another scheme.

ROUTE/DASH SLS can include the user service bundle description (USBD)and service-based transport session instance description (S-TSID)metadata fragments. These service signaling fragments are applicable toboth linear and application-based services. The USBD fragment containsservice identification, device capabilities information, references toother SLS fragments required to access the service and constituent mediacomponents, and metadata to enable the receiver to determine thetransport mode (broadcast and/or broadband) of service components. TheS-TSID fragment, referenced by the USBD, provides transport sessiondescriptions for the one or more ROUTE/LCT sessions in which the mediacontent components of a service are delivered, and descriptions of thedelivery objects carried in those LCT sessions. The USBD and S-TSID willbe described below.

In streaming content signaling in ROUTE-based delivery, a streamingcontent signaling component of SLS corresponds to an MPD fragment. TheMPD is typically associated with linear services for the delivery ofDASH Segments as streaming content. The MPD provides the resourceidentifiers for individual media components of the linear/streamingservice in the form of Segment URLs, and the context of the identifiedresources within the Media Presentation. Details of the MPD will bedescribed below.

In app-based enhancement signaling in ROUTE-based delivery, app-basedenhancement signaling pertains to the delivery of app-based enhancementcomponents, such as an application logic file, locally-cached mediafiles, network content items, or a notification stream. An applicationcan also retrieve locally-cached data over a broadband connection whenavailable.

Hereinafter, a description will be given of details of USBD/USDillustrated in the figure.

The top level or entry point SLS fragment is the USBD fragment. Anillustrated USBD fragment is an example of the present invention, basicfields of the USBD fragment not illustrated in the figure may beadditionally provided according to a given embodiment. As described inthe foregoing, the illustrated USBD fragment has an extended form, andmay have fields added to a basic configuration.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may correspond to aninstance for one service.

The userServiceDescription element may include @serviceId,@atsc:serviceId, @atsc:serviceStatus, @atsc:fullMPDUri, @atsc:sTSIDUri,name, serviceLanguage, atsc:capabilityCode and/or deliveryMethod.

@serviceId can be a globally unique URI that identifies a service,unique within the scope of the BSID. This parameter can be used to linkto ESG data (Service@globalServiceID).

@atsc:serviceId is a reference to corresponding service entry inLLS(SLT). The value of this attribute is the same value of serviceIdassigned to the entry.

@atsc:serviceStatus can specify the status of this service. The valueindicates whether this service is active or inactive. When set to “1”(true), that indicates service is active. When this field is not used,@atsc:serviceStatus may be set to a default value of 1.

@atsc:fullMPDUri can reference an MPD fragment which containsdescriptions for contents components of the service delivered overbroadcast and optionally, also over broadband.

@atsc:sTSIDUri can reference the S-TSID fragment which provides accessrelated parameters to the Transport sessions carrying contents of thisservice.

name can indicate name of the service as given by the lang attribute.name element can include lang attribute, which indicating language ofthe service name. The language can be specified according to XML datatypes.

serviceLanguage can represent available languages of the service. Thelanguage can be specified according to XML data types.

atsc:capabilityCode can specify the capabilities required in thereceiver to be able to create a meaningful presentation of the contentof this service. According to a given embodiment, this field may specifya predefined capability group. Here, the capability group may be a groupof capability attribute values for significant presentation. This fieldmay be omitted according to a given embodiment.

deliveryMethod can be a container of transport related informationpertaining to the contents of the service over broadcast and(optionally) broadband modes of access. Referring to data included inthe service, when the number of the data is N, delivery schemes forrespective data may be described by this element. The deliveryMethod mayinclude an r12:broadcastAppService element and an r12:unicastAppServiceelement. Each lower element may include a basePattern element as a lowerelement.

r12:broadcastAppService can be a DASH Representation delivered overbroadcast, in multiplexed or non-multiplexed form, containing thecorresponding media component(s) belonging to the service, across allPeriods of the affiliated media presentation. In other words, each ofthe fields may indicate DASH representation delivered through thebroadcast network.

r12:unicastAppService can be a DASH Representation delivered overbroadband, in multiplexed or non-multiplexed form, containing theconstituent media content component(s) belonging to the service, acrossall periods of the affiliated media presentation. In other words, eachof the fields may indicate DASH representation delivered via broadband.

basePattern can be a character pattern for use by the receiver to matchagainst any portion of the segment URL used by the DASH client torequest media segments of a parent representation under its containingperiod. A match implies that the corresponding requested media segmentis carried over broadcast transport. In a URL address for receiving DASHrepresentation expressed by each of the r12:broadcastAppService elementand the r12:unicastAppService element, a part of the URL, etc. may havea particular pattern. The pattern may be described by this field. Somedata may be distinguished using this information. The proposed defaultvalues may vary depending on embodiments. The “use” column illustratedin the figure relates to each field. Here, M may denote an essentialfield, O may denote an optional field, OD may denote an optional fieldhaving a default value, and CM may denote a conditional essential field.0 . . . 1 to 0 . . . N may indicate the number of available fields.

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of the S-TSID illustrated inthe figure in detail.

S-TSID can be an SLS XML fragment which provides the overall sessiondescription information for transport session(s) which carry the contentcomponents of a service. The S-TSID is the SLS metadata fragment thatcontains the overall transport session description information for thezero or more ROUTE sessions and constituent LCT sessions in which themedia content components of a service are delivered. The S-TSID alsoincludes file metadata for the delivery object or object flow carried inthe LCT sessions of the service, as well as additional information onthe payload formats and content components carried in those LCTsessions.

Each instance of the S-TSID fragment is referenced in the USBD fragmentby the @atsc:sTSIDUri attribute of the userServiceDescription element.The illustrated S-TSID according to the present embodiment is expressedas an XML document. According to a given embodiment, the S-TSID may beexpressed in a binary format or as an XML document.

The illustrated S-TSID may have an S-TSID root element. The S-TSID rootelement may include @serviceId and/or RS.

@serviceID can be a reference corresponding service element in the USD.The value of this attribute can reference a service with a correspondingvalue of service_id.

The RS element may have information about a ROUTE session for deliveringthe service data. Service data or service components may be deliveredthrough a plurality of ROUTE sessions, and thus the number of RSelements may be 1 to N.

The RS element may include @bsid, @sIpAddr, @dIpAddr, @dport, @PLPIDand/or LS.

@bsid can be an identifier of the broadcast stream within which thecontent component(s) of the broadcastAppService are carried. When thisattribute is absent, the default broadcast stream is the one whose PLPscarry SLS fragments for this service. Its value can be identical to thatof the broadcast_stream_id in the SLT.

@sIpAddr can indicate source IP address. Here, the source IP address maybe a source IP address of a ROUTE session for delivering a servicecomponent included in the service. As described in the foregoing,service components of one service may be delivered through a pluralityof ROUTE sessions. Thus, the service components may be transmitted usinganother ROUTE session other than the ROUTE session for delivering theS-TSID. Therefore, this field may be used to indicate the source IPaddress of the ROUTE session. A default value of this field may be asource IP address of a current ROUTE session. When a service componentis delivered through another ROUTE session, and thus the ROUTE sessionneeds to be indicated, a value of this field may be a value of a sourceIP address of the ROUTE session. In this case, this field may correspondto M, that is, an essential field.

@dIpAddr can indicate destination IP address. Here, a destination IPaddress may be a destination IP address of a ROUTE session that deliversa service component included in a service. For a similar case to theabove description of @sIpAddr, this field may indicate a destination IPaddress of a ROUTE session that delivers a service component. A defaultvalue of this field may be a destination IP address of a current ROUTEsession. When a service component is delivered through another ROUTEsession, and thus the ROUTE session needs to be indicated, a value ofthis field may be a value of a destination IP address of the ROUTEsession. In this case, this field may correspond to M, that is, anessential field.

@dport can indicate destination port. Here, a destination port may be adestination port of a ROUTE session that delivers a service componentincluded in a service. For a similar case to the above description of@sIpAddr, this field may indicate a destination port of a ROUTE sessionthat delivers a service component. A default value of this field may bea destination port number of a current ROUTE session. When a servicecomponent is delivered through another ROUTE session, and thus the ROUTEsession needs to be indicated, a value of this field may be adestination port number value of the ROUTE session. In this case, thisfield may correspond to M, that is, an essential field.

@PLPID may be an ID of a PLP for a ROUTE session expressed by an RS. Adefault value may be an ID of a PLP of an LCT session including acurrent S-TSID. According to a given embodiment, this field may have anID value of a PLP for an LCT session for delivering an S-TSID in theROUTE session, and may have ID values of all PLPs for the ROUTE session.

An LS element may have information about an LCT session for delivering aservice data. Service data or service components may be deliveredthrough a plurality of LCT sessions, and thus the number of LS elementsmay be 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime,SrcFlow and/or RprFlow.

@tsi may indicate a TSI value of an LCT session for delivering a servicecomponent of a service.

@PLPID may have ID information of a PLP for the LCT session. This valuemay be overwritten on a basic ROUTE session value.

@bw may indicate a maximum bandwidth value. @startTime may indicate astart time of the LCT session. @endTime may indicate an end time of theLCT session. A SrcFlow element may describe a source flow of ROUTE. ARprFlow element may describe a repair flow of ROUTE.

The proposed default values may be varied according to an embodiment.The “use” column illustrated in the figure relates to each field. Here,M may denote an essential field, O may denote an optional field, OD maydenote an optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for ROUTE/DASH.

The MPD is an SLS metadata fragment which contains a formalizeddescription of a DASH Media Presentation, corresponding to a linearservice of a given duration defined by the broadcaster (for example asingle TV program, or the set of contiguous linear TV programs over aperiod of time). The contents of the MPD provide the resourceidentifiers for Segments and the context for the identified resourceswithin the Media Presentation. The data structure and semantics of theMPD fragment can be according to the MPD defined by MPEG DASH.

One or more of the DASH Representations conveyed in the MPD can becarried over broadcast. The MPD may describe additional Representationsdelivered over broadband, e.g. in the case of a hybrid service, or tosupport service continuity in handoff from broadcast to broadcast due tobroadcast signal degradation (e.g. driving through a tunnel).

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention.

MMT SLS for linear services comprises the USBD fragment and the MMTPackage (MP) table. The MP table is as described above. The USBDfragment contains service identification, device capabilitiesinformation, references to other SLS information required to access theservice and constituent media components, and the metadata to enable thereceiver to determine the transport mode (broadcast and/or broadband) ofthe service components. The MP table for MPU components, referenced bythe USBD, provides transport session descriptions for the MMTP sessionsin which the media content components of a service are delivered and thedescriptions of the Assets carried in those MMTP sessions.

The streaming content signaling component of the SLS for MPU componentscorresponds to the MP table defined in MMT. The MP table provides a listof MMT assets where each asset corresponds to a single service componentand the description of the location information for this component.

USBD fragments may also contain references to the S-TSID and the MPD asdescribed above, for service components delivered by the ROUTE protocoland the broadband, respectively. According to a given embodiment, indelivery through MMT, a service component delivered through the ROUTEprotocol is NRT data, etc. Thus, in this case, MPD may be unnecessary.In addition, in delivery through MMT, information about an LCT sessionfor delivering a service component, which is delivered via broadband, isunnecessary, and thus an S-TSID may be unnecessary. Here, an MMT packagemay be a logical collection of media data delivered using MMT. Here, anMMTP packet may refer to a formatted unit of media data delivered usingMMT. An MPU may refer to a generic container of independently decodabletimed/non-timed data. Here, data in the MPU is media codec agnostic.

Hereinafter, a description will be given of details of the USBD/USDillustrated in the figure.

The illustrated USBD fragment is an example of the present invention,and basic fields of the USBD fragment may be additionally providedaccording to an embodiment. As described in the foregoing, theillustrated USBD fragment has an extended form, and may have fieldsadded to a basic structure.

The illustrated USBD according to an embodiment of the present inventionis expressed as an XML document. According to a given embodiment, theUSBD may be expressed in a binary format or as an XML document.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may be an instance for oneservice.

The userServiceDescription element may include @serviceId,@atsc:serviceId, name, serviceLanguage, atsc:capabilityCode,atsc:Channel, atsc:mpuComponent, atsc:routeComponent,atsc:broadbandComponent and/or atsc:ComponentInfo.

Here, @serviceId, @atsc:serviceId, name, serviceLanguage, andatsc:capabilityCode may be as described above. The lang field below thename field may be as described above. atsc:capabilityCode may be omittedaccording to a given embodiment.

The userServiceDescription element may further include anatsc:contentAdvisoryRating element according to an embodiment. Thiselement may be an optional element. atsc:contentAdvisoryRating canspecify the content advisory rating. This field is not illustrated inthe figure.

atsc:Channel may have information about a channel of a service. Theatsc:Channel element may include @atsc:majorChannelNo,@atsc:minorChannelNo, @atsc:serviceLang, @atsc:serviceGenre,@atsc:servicelcon and/or atsc:ServiceDescription. @atsc:majorChannelNo,@atsc:minorChannelNo, and @atsc:serviceLang may be omitted according toa given embodiment.

@atsc:majorChannelNo is an attribute that indicates the major channelnumber of the service.

@atsc:minorChannelNo is an attribute that indicates the minor channelnumber of the service.

@atsc:serviceLang is an attribute that indicates the primary languageused in the service.

@atsc:serviceGenre is an attribute that indicates primary genre of theservice.

@atsc:servicelcon is an attribute that indicates the Uniform ResourceLocator (URL) for the icon used to represent this service.

atsc:ServiceDescription includes service description, possibly inmultiple languages. atsc:ServiceDescription includes can include@atsc:serviceDescrText and/or @atsc:serviceDescrLang.

@atsc:serviceDescrText is an attribute that indicates description of theservice.

@atsc:serviceDescrLang is an attribute that indicates the language ofthe serviceDescrText attribute above.

atsc:mpuComponent may have information about a content component of aservice delivered in a form of an MPU. atsc:mpuComponent may include@atsc:mmtPackageId and/or @atsc:nextMmtPackageId.

@atsc:mmtPackageId can reference a MMT Package for content components ofthe service delivered as MPUs.

@atsc:nextMmtPackageId can reference a MMT Package to be used after theone referenced by @atsc:mmtPackageId in time for content components ofthe service delivered as MPUs.

atsc:routeComponent may have information about a content component of aservice delivered through ROUTE. atsc:routeComponent may include@atsc:sTSIDUri, @sTSIDPIpId, @sTSIDDestinationIpAddress,@sTSIDDestinationUdpPort, @sTSIDSourceIpAddress,@sTSIDMajorProtocolVersion and/or @sTSIDMinorProtocolVersion.

@atsc:sTSIDUri can be a reference to the S-TSID fragment which providesaccess related parameters to the Transport sessions carrying contents ofthis service. This field may be the same as a URI for referring to anS-TSID in USBD for ROUTE described above. As described in the foregoing,in service delivery by the MMTP, service components, which are deliveredthrough NRT, etc., may be delivered by ROUTE. This field may be used torefer to the S-TSID therefor.

@sTSIDPIpId can be a string representing an integer number indicatingthe PLP ID of the physical layer pipe carrying the S-TSID for thisservice. (default: current physical layer pipe).

@sTSIDDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying S-TSID for this service.(default: current MMTP session's source IP address)

@sTSIDDestinationUdpPort can be a string containing the port number ofthe packets carrying S-TSID for this service.

@sTSIDSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying S-TSID for this service.

@sTSIDMajorProtocolVersion can indicate major version number of theprotocol used to deliver the S-TSID for this service. Default value is1.

@sTSIDMinorProtocolVersion can indicate minor version number of theprotocol used to deliver the S-TSID for this service. Default value is0.

atsc:broadbandComponent may have information about a content componentof a service delivered via broadband. In other words,atsc:broadbandComponent may be a field on the assumption of hybriddelivery. atsc:broadbandComponent may further include @atsc:fullfMPDUri.

@atsc:fullfMPDUri can be a reference to an MPD fragment which containsdescriptions for contents components of the service delivered overbroadband.

An atsc:ComponentInfo field may have information about an availablecomponent of a service. The atsc:ComponentInfo field may haveinformation about a type, a role, a name, etc. of each component. Thenumber of atsc:ComponentInfo fields may correspond to the number (N) ofrespective components. The atsc:ComponentInfo field may include@atsc:componentType, @atsc:componentRole, @atsc:componentProtectedFlag,@atsc:componentld and/or @atsc:componentName.

@atsc:componentType is an attribute that indicates the type of thiscomponent. Value of 0 indicates an audio component. Value of 1 indicatesa video component. Value of 2 indicated a closed caption component.Value of 3 indicates an application component. Values 4 to 7 arereserved. A meaning of a value of this field may be differently setdepending on embodiments.

@atsc:componentRole is an attribute that indicates the role or kind ofthis component.

For audio (when componentType attribute above is equal to 0): values ofcomponentRole attribute are as follows: 0=Complete main, 1=Music andEffects, 2=Dialog, 3=Commentary, 4=Visually Impaired, 5=HearingImpaired, 6=Voice-Over, 7-254=reserved, 255=unknown.

For video (when componentType attribute above is equal to 1) values ofcomponentRole attribute are as follows: 0=Primary video, 1=Alternativecamera view, 2=Other alternative video component, 3=Sign language inset,4=Follow subject video, 5=3D video left view, 6=3D video right view,7=3D video depth information, 8=Part of video array <x,y> of <n,m>,9=Follow-Subject metadata, 10-254=reserved, 255=unknown.

For Closed Caption component (when componentType attribute above isequal to 2) values of componentRole attribute are as follows: 0=Normal,1=Easy reader, 2-254=reserved, 255=unknown.

When componentType attribute above is between 3 to 7, inclusive, thecomponentRole can be equal to 255. A meaning of a value of this fieldmay be differently set depending on embodiments.

@atsc:componentProtectedFlag is an attribute that indicates if thiscomponent is protected (e.g. encrypted). When this flag is set to avalue of 1 this component is protected (e.g. encrypted). When this flagis set to a value of 0 this component is not protected (e.g. encrypted).When not present the value of componentProtectedFlag attribute isinferred to be equal to 0. A meaning of a value of this field may bedifferently set depending on embodiments.

@atsc:componentld is an attribute that indicates the identifier of thiscomponent. The value of this attribute can be the same as the asset_idin the MP table corresponding to this component.

@atsc:componentName is an attribute that indicates the human readablename of this component.

The proposed default values may vary depending on embodiments. The “use”column illustrated in the figure relates to each field. Here, M maydenote an essential field, O may denote an optional field, OD may denotean optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for MMT.

The Media Presentation Description is an SLS metadata fragmentcorresponding to a linear service of a given duration defined by thebroadcaster (for example a single TV program, or the set of contiguouslinear TV programs over a period of time). The contents of the MPDprovide the resource identifiers for segments and the context for theidentified resources within the media presentation. The data structureand semantics of the MPD can be according to the MPD defined by MPEGDASH.

In the present embodiment, an MPD delivered by an MMTP session describesRepresentations delivered over broadband, e.g. in the case of a hybridservice, or to support service continuity in handoff from broadcast tobroadband due to broadcast signal degradation (e.g. driving under amountain or through a tunnel).

Hereinafter, a description will be given of an MMT signaling message forMMT.

When MMTP sessions are used to carry a streaming service, MMT signalingmessages defined by MMT are delivered by MMTP packets according tosignaling message mode defined by MMT. The value of the packet_id fieldof MMTP packets carrying service layer signaling is set to ‘00’ exceptfor MMTP packets carrying MMT signaling messages specific to an asset,which can be set to the same packet_id value as the MMTP packetscarrying the asset. Identifiers referencing the appropriate package foreach service are signaled by the USBD fragment as described above. MMTPackage Table (MPT) messages with matching MMT_package_id can bedelivered on the MMTP session signaled in the SLT. Each MMTP sessioncarries MMT signaling messages specific to its session or each assetdelivered by the MMTP session.

In other words, it is possible to access USBD of the MMTP session byspecifying an IP destination address/port number, etc. of a packethaving the SLS for a particular service in the SLT. As described in theforegoing, a packet ID of an MMTP packet carrying the SLS may bedesignated as a particular value such as 00, etc. It is possible toaccess an MPT message having a matched packet ID using theabove-described package IP information of USBD. As described below, theMPT message may be used to access each service component/asset.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT.

MMT Package Table (MPT) message: This message carries an MP (MMTPackage) table which contains the list of all Assets and their locationinformation as defined by MMT. If an Asset is delivered by a PLPdifferent from the current PLP delivering the MP table, the identifierof the PLP carrying the asset can be provided in the MP table usingphysical layer pipe identifier descriptor. The physical layer pipeidentifier descriptor will be described below.

MMT ATSC3 (MA3) message mmt_atsc3_message( ): This message carriessystem metadata specific for services including service layer signalingas described above. mmt_atsc3_message( ) will be described below.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT, if required.

Media Presentation Information (MPI) message: This message carries anMPI table which contains the whole document or a subset of a document ofpresentation information. An MP table associated with the MPI table alsocan be delivered by this message.

Clock Relation Information (CRI) message: This message carries a CRItable which contains clock related information for the mapping betweenthe NTP timestamp and the MPEG-2 STC. According to a given embodiment,the CRI message may not be delivered through the MMTP session.

The following MMTP messages can be delivered by each MMTP sessioncarrying streaming content.

Hypothetical Receiver Buffer Model message: This message carriesinformation required by the receiver to manage its buffer.

Hypothetical Receiver Buffer Model Removal message: This message carriesinformation required by the receiver to manage its MMT de-capsulationbuffer.

Hereinafter, a description will be given of mmt_atsc3_message( )corresponding to one of MMT signaling messages. An MMT Signaling messagemmt_atsc3_message( ) is defined to deliver information specific toservices according to the present invention described above. Thesignaling message may include message ID, version, and/or length fieldscorresponding to basic fields of the MMT signaling message. A payload ofthe signaling message may include service ID information, content typeinformation, content version information, content compressioninformation and/or URI information. The content type information mayindicate a type of data included in the payload of the signalingmessage. The content version information may indicate a version of dataincluded in the payload, and the content compression information mayindicate a type of compression applied to the data. The URI informationmay have URI information related to content delivered by the message.

Hereinafter, a description will be given of the physical layer pipeidentifier descriptor.

The physical layer pipe identifier descriptor is a descriptor that canbe used as one of descriptors of the MP table described above. Thephysical layer pipe identifier descriptor provides information about thePLP carrying an asset. If an asset is delivered by a PLP different fromthe current PLP delivering the MP table, the physical layer pipeidentifier descriptor can be used as an asset descriptor in theassociated MP table to identify the PLP carrying the asset. The physicallayer pipe identifier descriptor may further include BSID information inaddition to PLP ID information. The BSID may be an ID of a broadcaststream that delivers an MMTP packet for an asset described by thedescriptor.

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention.

Hereinafter, a link layer will be described.

The link layer is the layer between the physical layer and the networklayer, and transports the data from the network layer to the physicallayer at the sending side and transports the data from the physicallayer to the network layer at the receiving side. The purpose of thelink layer includes abstracting all input packet types into a singleformat for processing by the physical layer, ensuring flexibility andfuture extensibility for as yet undefined input types. In addition,processing within the link layer ensures that the input data can betransmitted in an efficient manner, for example by providing options tocompress redundant information in the headers of input packets. Theoperations of encapsulation, compression and so on are referred to asthe link layer protocol and packets created using this protocol arecalled link layer packets. The link layer may perform functions such aspacket encapsulation, overhead reduction and/or signaling transmission,etc.

Hereinafter, packet encapsulation will be described. Link layer protocolallows encapsulation of any type of packet, including ones such as IPpackets and MPEG-2 TS. Using link layer protocol, the physical layerneed only process one single packet format, independent of the networklayer protocol type (here we consider MPEG-2 TS packet as a kind ofnetwork layer packet.) Each network layer packet or input packet istransformed into the payload of a generic link layer packet.Additionally, concatenation and segmentation can be performed in orderto use the physical layer resources efficiently when the input packetsizes are particularly small or large.

As described in the foregoing, segmentation may be used in packetencapsulation. When the network layer packet is too large to processeasily in the physical layer, the network layer packet is divided intotwo or more segments. The link layer packet header includes protocolfields to perform segmentation on the sending side and reassembly on thereceiving side. When the network layer packet is segmented, each segmentcan be encapsulated to link layer packet in the same order as originalposition in the network layer packet. Also each link layer packet whichincludes a segment of network layer packet can be transported to PHYlayer consequently.

As described in the foregoing, concatenation may be used in packetencapsulation. When the network layer packet is small enough for thepayload of a link layer packet to include several network layer packets,the link layer packet header includes protocol fields to performconcatenation. The concatenation is combining of multiple small sizednetwork layer packets into one payload. When the network layer packetsare concatenated, each network layer packet can be concatenated topayload of link layer packet in the same order as original input order.Also each packet which constructs a payload of link layer packet can bewhole packet, not a segment of packet.

Hereinafter, overhead reduction will be described. Use of the link layerprotocol can result in significant reduction in overhead for transportof data on the physical layer. The link layer protocol according to thepresent invention may provide IP overhead reduction and/or MPEG-2 TSoverhead reduction. In IP overhead reduction, IP packets have a fixedheader format, however some of the information which is needed in acommunication environment may be redundant in a broadcast environment.Link layer protocol provides mechanisms to reduce the broadcast overheadby compressing headers of IP packets. In MPEG-2 TS overhead reduction,link layer protocol provides sync byte removal, null packet deletionand/or common header removal (compression). First, sync byte removalprovides an overhead reduction of one byte per TS packet, secondly anull packet deletion mechanism removes the 188 byte null TS packets in amanner that they can be re-inserted at the receiver and finally a commonheader removal mechanism.

For signaling transmission, in the link layer protocol, a particularformat for the signaling packet may be provided for link layersignaling, which will be described below.

In the illustrated link layer protocol architecture according to anembodiment of the present invention, link layer protocol takes as inputnetwork layer packets such as IPv4, MPEG-2 TS and so on as inputpackets. Future extension indicates other packet types and protocolwhich is also possible to be input in link layer. Link layer protocolalso specifies the format and signaling for any link layer signaling,including information about mapping to specific channel to the physicallayer. Figure also shows how ALP incorporates mechanisms to improve theefficiency of transmission, via various header compression and deletionalgorithms. In addition, the link layer protocol may basicallyencapsulate input packets.

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention. Hereinafter, thestructure of the header will be described.

A link layer packet can include a header followed by the data payload.The header of a link layer packet can include a base header, and mayinclude an additional header depending on the control fields of the baseheader. The presence of an optional header is indicated from flag fieldsof the additional header. According to a given embodiment, a fieldindicating the presence of an additional header and an optional headermay be positioned in the base header.

Hereinafter, the structure of the base header will be described. Thebase header for link layer packet encapsulation has a hierarchicalstructure. The base header can be two bytes in length and is the minimumlength of the link layer packet header.

The illustrated base header according to the present embodiment mayinclude a Packet_Type field, a PC field and/or a length field. Accordingto a given embodiment, the base header may further include an HM fieldor an S/C field.

Packet_Type field can be a 3-bit field that indicates the originalprotocol or packet type of the input data before encapsulation into alink layer packet. An IPv4 packet, a compressed IP packet, a link layersignaling packet, and other types of packets may have the base headerstructure and may be encapsulated. However, according to a givenembodiment, the MPEG-2 TS packet may have a different particularstructure, and may be encapsulated. When the value of Packet_Type is“000”, “001” “100” or “111”, that is the original data type of an ALPpacket is one of an IPv4 packet, a compressed IP packet, link layersignaling or extension packet. When the MPEG-2 TS packet isencapsulated, the value of Packet_Type can be “010”. Other values of thePacket_Type field may be reserved for future use.

Payload_Configuration (PC) field can be a 1-bit field that indicates theconfiguration of the payload. A value of 0 can indicate that the linklayer packet carries a single, whole input packet and the followingfield is the Header_Mode field. A value of 1 can indicate that the linklayer packet carries more than one input packet (concatenation) or apart of a large input packet (segmentation) and the following field isthe Segmentation_Concatenation field.

Header_Mode (HM) field can be a 1-bit field, when set to 0, that canindicate there is no additional header, and that the length of thepayload of the link layer packet is less than 2048 bytes. This value maybe varied depending on embodiments. A value of 1 can indicate that anadditional header for single packet defined below is present followingthe Length field. In this case, the length of the payload is larger than2047 bytes and/or optional features can be used (sub streamidentification, header extension, etc.). This value may be varieddepending on embodiments. This field can be present only whenPayload_Configuration field of the link layer packet has a value of 0.

Segmentation_Concatenation (S/C) field can be a 1-bit field, when set to0, that can indicate that the payload carries a segment of an inputpacket and an additional header for segmentation defined below ispresent following the Length field. A value of 1 can indicate that thepayload carries more than one complete input packet and an additionalheader for concatenation defined below is present following the Lengthfield. This field can be present only when the value ofPayload_Configuration field of the ALP packet is 1.

Length field can be a 11-bit field that indicates the 11 leastsignificant bits (LSBs) of the length in bytes of payload carried by thelink layer packet. When there is a Length_MSB field in the followingadditional header, the length field is concatenated with the Length_MSBfield, and is the LSB to provide the actual total length of the payload.The number of bits of the length field may be changed to another valuerather than 11 bits.

Following types of packet configuration are thus possible: a singlepacket without any additional header, a single packet with an additionalheader, a segmented packet and a concatenated packet. According to agiven embodiment, more packet configurations may be made through acombination of each additional header, an optional header, an additionalheader for signaling information to be described below, and anadditional header for time extension.

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention.

Various types of additional headers may be present. Hereinafter, adescription will be given of an additional header for a single packet.

This additional header for single packet can be present when Header_Mode(HM)=“1”. The Header Mode (HM) can be set to 1 when the length of thepayload of the link layer packet is larger than 2047 bytes or when theoptional fields are used. The additional header for single packet isshown in Figure (tsib10010).

Length_MSB field can be a 5-bit field that can indicate the mostsignificant bits (MSBs) of the total payload length in bytes in thecurrent link layer packet, and is concatenated with the Length fieldcontaining the 11 least significant bits (LSBs) to obtain the totalpayload length. The maximum length of the payload that can be signaledis therefore 65535 bytes. The number of bits of the length field may bechanged to another value rather than 11 bits. In addition, the number ofbits of the Length_MSB field may be changed, and thus a maximumexpressible payload length may be changed. According to a givenembodiment, each length field may indicate a length of a whole linklayer packet rather than a payload.

SIF (Sub stream Identifier Flag) field can be a 1-bit field that canindicate whether the sub stream ID (SID) is present after the HEF fieldor not. When there is no SID in this link layer packet, SIF field can beset to 0. When there is a SID after HEF field in the link layer packet,SIF can be set to 1. The detail of SID is described below.

HEF (Header Extension Flag) field can be a 1-bit field that canindicate, when set to 1 additional header is present for futureextension. A value of 0 can indicate that this extension header is notpresent.

Hereinafter, a description will be given of an additional header whensegmentation is used.

This additional header (tsib10020) can be present whenSegmentation_Concatenation (S/C)=“0”. Segment_Sequence_Number can be a5-bit unsigned integer that can indicate the order of the correspondingsegment carried by the link layer packet. For the link layer packetwhich carries the first segment of an input packet, the value of thisfield can be set to 0x0. This field can be incremented by one with eachadditional segment belonging to the segmented input packet.

Last_Segment_Indicator (LSI) can be a 1-bit field that can indicate,when set to 1, that the segment in this payload is the last one of inputpacket. A value of 0, can indicate that it is not last segment.

SIF (Sub stream Identifier Flag) can be a 1-bit field that can indicatewhether the SID is present after the HEF field or not. When there is noSID in the link layer packet, SIF field can be set to 0. When there is aSID after the HEF field in the link layer packet, SIF can be set to 1.

HEF (Header Extension Flag) can be a This 1-bit field that can indicate,when set to 1, that the optional header extension is present after theadditional header for future extensions of the link layer header. Avalue of 0 can indicate that optional header extension is not present.

According to a given embodiment, a packet ID field may be additionallyprovided to indicate that each segment is generated from the same inputpacket. This field may be unnecessary and thus be omitted when segmentsare transmitted in order.

Hereinafter, a description will be given of an additional header whenconcatenation is used.

This additional header (tsib10030) can be present whenSegmentation_Concatenation (S/C)=“1”.

Length_MSB can be a 4-bit field that can indicate MSB bits of thepayload length in bytes in this link layer packet. The maximum length ofthe payload is 32767 bytes for concatenation. As described in theforegoing, a specific numeric value may be changed.

Count can be a field that can indicate the number of the packetsincluded in the link layer packet. The number of the packets included inthe link layer packet, 2 can be set to this field. So, its maximum valueof concatenated packets in a link layer packet is 9. A scheme in whichthe count field indicates the number may be varied depending onembodiments. That is, the numbers from 1 to 8 may be indicated.

HEF (Header Extension Flag) can be a 1-bit field that can indicate, whenset to 1 the optional header extension is present after the additionalheader for future extensions of the link layer header. A value of 0, canindicate extension header is not present.

Component Length can be a 12-bit length field that can indicate thelength in byte of each packet. Component_Length fields are included inthe same order as the packets present in the payload except lastcomponent packet. The number of length field can be indicated by(Count+1). According to a given embodiment, length fields, the number ofwhich is the same as a value of the count field, may be present. When alink layer header consists of an odd number of Component_Length, fourstuffing bits can follow after the last Component_Length field. Thesebits can be set to 0. According to a given embodiment, aComponent_length field indicating a length of a last concatenated inputpacket may not be present. In this case, the length of the lastconcatenated input packet may correspond to a length obtained bysubtracting a sum of values indicated by respective Component_lengthfields from a whole payload length.

Hereinafter, the optional header will be described.

As described in the foregoing, the optional header may be added to arear of the additional header. The optional header field can contain SIDand/or header extension. The SID is used to filter out specific packetstream in the link layer level. One example of SID is the role ofservice identifier in a link layer stream carrying multiple services.The mapping information between a service and the SID valuecorresponding to the service can be provided in the SLT, if applicable.The header extension contains extended field for future use. Receiverscan ignore any header extensions which they do not understand.

SID (Sub stream Identifier) can be a 8-bit field that can indicate thesub stream identifier for the link layer packet. If there is optionalheader extension, SID present between additional header and optionalheader extension.

Header_Extension ( ) can include the fields defined below.

Extension_Type can be an 8-bit field that can indicate the type of theHeader_Extension ( ).

Extension_Length can be a 8-bit field that can indicate the length ofthe Header Extension ( ) in bytes counting from the next byte to thelast byte of the Header_Extension ( ).

Extension Byte can be a byte representing the value of theHeader_Extension ( ).

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention.

Hereinafter, a description will be given of an additional header forsignaling information.

How link layer signaling is incorporated into link layer packets are asfollows. Signaling packets are identified by when the Packet_Type fieldof the base header is equal to 100.

Figure (tsib11010) shows the structure of the link layer packetscontaining additional header for signaling information. In addition tothe link layer header, the link layer packet can consist of twoadditional parts, additional header for signaling information and theactual signaling data itself. The total length of the link layersignaling packet is shown in the link layer packet header.

The additional header for signaling information can include followingfields. According to a given embodiment, some fields may be omitted.

Signaling_Type can be an 8-bit field that can indicate the type ofsignaling.

Signaling_Type_Extension can be a 16-bit filed that can indicate theattribute of the signaling. Detail of this field can be defined insignaling specification.

Signaling_Version can be an 8-bit field that can indicate the version ofsignaling.

Signaling_Format can be a 2-bit field that can indicate the data formatof the signaling data. Here, a signaling format may refer to a dataformat such as a binary format, an XML format, etc.

Signaling_Encoding can be a 2-bit field that can specify theencoding/compression format. This field may indicate whether compressionis not performed and which type of compression is performed.

Hereinafter, a description will be given of an additional header forpacket type extension.

In order to provide a mechanism to allow an almost unlimited number ofadditional protocol and packet types to be carried by link layer in thefuture, the additional header is defined. Packet type extension can beused when Packet_type is 111 in the base header as described above.Figure (tsib11020) shows the structure of the link layer packetscontaining additional header for type extension.

The additional header for type extension can include following fields.According to a given embodiment, some fields may be omitted.

extended_type can be a 16-bit field that can indicate the protocol orpacket type of the input encapsulated in the link layer packet aspayload. This field cannot be used for any protocol or packet typealready defined by Packet_Type field.

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention.

Hereinafter, a description will be given of a format of the link layerpacket when the MPEG-2 TS packet is input as an input packet.

In this case, the Packet_Type field of the base header is equal to 010.Multiple TS packets can be encapsulated within each link layer packet.The number of TS packets is signaled via the NUMTS field. In this case,as described in the foregoing, a particular link layer packet headerformat may be used.

Link layer provides overhead reduction mechanisms for MPEG-2 TS toenhance the transmission efficiency. The sync byte (0x47) of each TSpacket can be deleted. The option to delete NULL packets and similar TSheaders is also provided.

In order to avoid unnecessary transmission overhead, TS null packets(PID=0x1FFF) may be removed. Deleted null packets can be recovered inreceiver side using DNP field. The DNP field indicates the count ofdeleted null packets. Null packet deletion mechanism using DNP field isdescribed below.

In order to achieve more transmission efficiency, similar header ofMPEG-2 TS packets can be removed. When two or more successive TS packetshave sequentially increased continuity counter fields and other headerfields are the same, the header is sent once at the first packet and theother headers are deleted. HDM field can indicate whether the headerdeletion is performed or not. Detailed procedure of common TS headerdeletion is described below.

When all three overhead reduction mechanisms are performed, overheadreduction can be performed in sequence of sync removal, null packetdeletion, and common header deletion. According to a given embodiment, aperformance order of respective mechanisms may be changed. In addition,some mechanisms may be omitted according to a given embodiment.

The overall structure of the link layer packet header when using MPEG-2TS packet encapsulation is depicted in Figure (tsib12010).

Hereinafter, a description will be given of each illustrated field.Packet_Type can be a 3-bit field that can indicate the protocol type ofinput packet as describe above. For MPEG-2 TS packet encapsulation, thisfield can always be set to 010.

NUMTS (Number of TS packets) can be a 4-bit field that can indicate thenumber of TS packets in the payload of this link layer packet. A maximumof 16 TS packets can be supported in one link layer packet. The value ofNUMTS=0 can indicate that 16 TS packets are carried by the payload ofthe link layer packet. For all other values of NUMTS, the same number ofTS packets are recognized, e.g. NUMTS=0001 means one TS packet iscarried.

AHF (Additional Header Flag) can be a field that can indicate whetherthe additional header is present of not. A value of 0 indicates thatthere is no additional header. A value of 1 indicates that an additionalheader of length 1-byte is present following the base header. If null TSpackets are deleted or TS header compression is applied this field canbe set to 1. The additional header for TS packet encapsulation consistsof the following two fields and is present only when the value of AHF inthis link layer packet is set to 1.

HDM (Header Deletion Mode) can be a 1-bit field that indicates whetherTS header deletion can be applied to this link layer packet. A value of1 indicates that TS header deletion can be applied. A value of “0”indicates that the TS header deletion method is not applied to this linklayer packet.

DNP (Deleted Null Packets) can be a 7-bit field that indicates thenumber of deleted null TS packets prior to this link layer packet. Amaximum of 128 null TS packets can be deleted. When HDM=0 the value ofDNP=0 can indicate that 128 null packets are deleted. When HDM=1 thevalue of DNP=0 can indicate that no null packets are deleted. For allother values of DNP, the same number of null packets are recognized,e.g. DNP=5 means 5 null packets are deleted.

The number of bits of each field described above may be changed.According to the changed number of bits, a minimum/maximum value of avalue indicated by the field may be changed. These numbers may bechanged by a designer.

Hereinafter, SYNC byte removal will be described.

When encapsulating TS packets into the payload of a link layer packet,the SYNC byte (0x47) from the start of each TS packet can be deleted.Hence the length of the MPEG2-TS packet encapsulated in the payload ofthe link layer packet is always of length 187 bytes (instead of 188bytes originally).

Hereinafter, null packet deletion will be described.

Transport Stream rules require that bit rates at the output of atransmitter's multiplexer and at the input of the receiver'sde-multiplexer are constant in time and the end-to-end delay is alsoconstant. For some Transport Stream input signals, null packets may bepresent in order to accommodate variable bitrate services in a constantbitrate stream. In this case, in order to avoid unnecessary transmissionoverhead, TS null packets (that is TS packets with PID=0x1FFF) may beremoved. The process is carried-out in a way that the removed nullpackets can be re-inserted in the receiver in the exact place where theywere originally, thus guaranteeing constant bitrate and avoiding theneed for PCR time stamp updating.

Before generation of a link layer packet, a counter called DNP (DeletedNull-Packets) can first be reset to zero and then incremented for eachdeleted null packet preceding the first non-null TS packet to beencapsulated into the payload of the current link layer packet. Then agroup of consecutive useful TS packets is encapsulated into the payloadof the current link layer packet and the value of each field in itsheader can be determined. After the generated link layer packet isinjected to the physical layer, the DNP is reset to zero. When DNPreaches its maximum allowed value, if the next packet is also a nullpacket, this null packet is kept as a useful packet and encapsulatedinto the payload of the next link layer packet. Each link layer packetcan contain at least one useful TS packet in its payload.

Hereinafter, TS packet header deletion will be described. TS packetheader deletion may be referred to as TS packet header compression.

When two or more successive TS packets have sequentially increasedcontinuity counter fields and other header fields are the same, theheader is sent once at the first packet and the other headers aredeleted. When the duplicated MPEG-2 TS packets are included in two ormore successive TS packets, header deletion cannot be applied intransmitter side. HDM field can indicate whether the header deletion isperformed or not. When TS header deletion is performed, HDM can be setto 1. In the receiver side, using the first packet header, the deletedpacket headers are recovered, and the continuity counter is restored byincreasing it in order from that of the first header.

An example tsib12020 illustrated in the figure is an example of aprocess in which an input stream of a TS packet is encapsulated into alink layer packet. First, a TS stream including TS packets having SYNCbyte (0x47) may be input. First, sync bytes may be deleted through async byte deletion process. In this example, it is presumed that nullpacket deletion is not performed.

Here, it is presumed that packet headers of eight TS packets have thesame field values except for CC, that is, a continuity counter fieldvalue. In this case, TS packet deletion/compression may be performed.Seven remaining TS packet headers are deleted except for a first TSpacket header corresponding to CC=1. The processed TS packets may beencapsulated into a payload of the link layer packet.

In a completed link layer packet, a Packet_Type field corresponds to acase in which TS packets are input, and thus may have a value of 010. ANUMTS field may indicate the number of encapsulated TS packets. An AHFfield may be set to 1 to indicate the presence of an additional headersince packet header deletion is performed. An HDM field may be set to 1since header deletion is performed. DNP may be set to 0 since nullpacket deletion is not performed.

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side).

Hereinafter, IP header compression will be described.

In the link layer, IP header compression/decompression scheme can beprovided. IP header compression can include two parts: headercompressor/decompressor and adaptation module. The header compressionscheme can be based on the Robust Header Compression (RoHC). Inaddition, for broadcasting usage, adaptation function is added.

In the transmitter side, ROHC compressor reduces the size of header foreach packet. Then, adaptation module extracts context information andbuilds signaling information from each packet stream. In the receiverside, adaptation module parses the signaling information associated withthe received packet stream and attaches context information to thereceived packet stream. ROHC decompressor reconstructs the original IPpacket by recovering the packet header.

The header compression scheme can be based on the RoHC as describedabove. In particular, in the present system, an RoHC framework canoperate in a unidirctional mode (U mode) of the RoHC. In addition, inthe present system, it is possible to use an RoHC UDP header compressionprofile which is identified by a profile identifier of 0x0002.

Hereinafter, adaptation will be described.

In case of transmission through the unidirectional link, if a receiverhas no information of context, decompressor cannot recover the receivedpacket header until receiving full context. This may cause channelchange delay and turn on delay. For this reason, context information andconfiguration parameters between compressor and decompressor can bealways sent with packet flow.

The Adaptation function provides out-of-band transmission of theconfiguration parameters and context information. Out-of-bandtransmission can be done through the link layer signaling. Therefore,the adaptation function is used to reduce the channel change delay anddecompression error due to loss of context information.

Hereinafter, extraction of context information will be described.

Context information may be extracted using various schemes according toadaptation mode. In the present invention, three examples will bedescribed below. The scope of the present invention is not restricted tothe examples of the adaptation mode to be described below. Here, theadaptation mode may be referred to as a context extraction mode.

Adaptation Mode 1 (not illustrated) may be a mode in which no additionaloperation is applied to a basic RoHC packet stream. In other words, theadaptation module may operate as a buffer in this mode. Therefore, inthis mode, context information may not be included in link layersignaling

In Adaptation Mode 2 (tsib13010), the adaptation module can detect theIR packet from ROHC packet flow and extract the context information(static chain). After extracting the context information, each IR packetcan be converted to an IR-DYN packet. The converted IR-DYN packet can beincluded and transmitted inside the ROHC packet flow in the same orderas IR packet, replacing the original packet.

In Adaptation Mode 3 (tsib13020), the adaptation module can detect theIR and IR-DYN packet from ROHC packet flow and extract the contextinformation. The static chain and dynamic chain can be extracted from IRpacket and dynamic chain can be extracted from IR-DYN packet. Afterextracting the context information, each IR and IR-DYN packet can beconverted to a compressed packet. The compressed packet format can bethe same with the next packet of IR or IR-DYN packet. The convertedcompressed packet can be included and transmitted inside the ROHC packetflow in the same order as IR or IR-DYN packet, replacing the originalpacket.

Signaling (context) information can be encapsulated based ontransmission structure. For example, context information can beencapsulated to the link layer signaling. In this case, the packet typevalue can be set to “100”.

In the above-described Adaptation Modes 2 and 3, a link layer packet forcontext information may have a packet type field value of 100. Inaddition, a link layer packet for compressed IP packets may have apacket type field value of 001. The values indicate that each of thesignaling information and the compressed IP packets are included in thelink layer packet as described above.

Hereinafter, a description will be given of a method of transmitting theextracted context information.

The extracted context information can be transmitted separately fromROHC packet flow, with signaling data through specific physical datapath. The transmission of context depends on the configuration of thephysical layer path. The context information can be sent with other linklayer signaling through the signaling data pipe.

In other words, the link layer packet having the context information maybe transmitted through a signaling PLP together with link layer packetshaving other link layer signaling information (Packet_Type=100).Compressed IP packets from which context information is extracted may betransmitted through a general PLP (Packet_Type=001). Here, depending onembodiments, the signaling PLP may refer to an L1 signaling path. Inaddition, depending on embodiments, the signaling PLP may not beseparated from the general PLP, and may refer to a particular andgeneral PLP through which the signaling information is transmitted.

At a receiving side, prior to reception of a packet stream, a receivermay need to acquire signaling information. When receiver decodes initialPLP to acquire the signaling information, the context signaling can bealso received. After the signaling acquisition is done, the PLP toreceive packet stream can be selected. In other words, the receiver mayacquire the signaling information including the context information byselecting the initial PLP. Here, the initial PLP may be theabove-described signaling PLP. Thereafter, the receiver may select a PLPfor acquiring a packet stream. In this way, the context information maybe acquired prior to reception of the packet stream.

After the PLP for acquiring the packet stream is selected, theadaptation module can detect IR-DYN packet form received packet flow.Then, the adaptation module parses the static chain from the contextinformation in the signaling data. This is similar to receiving the IRpacket. For the same context identifier, IR-DYN packet can be recoveredto IR packet. Recovered ROHC packet flow can be sent to ROHCdecompressor. Thereafter, decompression may be started.

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention.

Hereinafter, link layer signaling will be described.

Generally, link layer signaling is operates under IP level. At thereceiver side, link layer signaling can be obtained earlier than IPlevel signaling such as Service List Table (SLT) and Service LayerSignaling (SLS). Therefore, link layer signaling can be obtained beforesession establishment.

For link layer signaling, there can be two kinds of signaling accordinginput path: internal link layer signaling and external link layersignaling. The internal link layer signaling is generated in link layerat transmitter side. And the link layer takes the signaling fromexternal module or protocol. This kind of signaling information isconsidered as external link layer signaling. If some signaling need tobe obtained prior to IP level signaling, external signaling istransmitted in format of link layer packet.

The link layer signaling can be encapsulated into link layer packet asdescribed above. The link layer packets can carry any format of linklayer signaling, including binary and XML. The same signalinginformation may not be transmitted in different formats for the linklayer signaling.

Internal link layer signaling may include signaling information for linkmapping. The Link Mapping Table (LMT) provides a list of upper layersessions carried in a PLP. The LMT also provides addition informationfor processing the link layer packets carrying the upper layer sessionsin the link layer.

An example of the LMT (tsib14010) according to the present invention isillustrated.

signaling_type can be an 8-bit unsigned integer field that indicates thetype of signaling carried by this table. The value of signaling_typefield for Link Mapping Table (LMT) can be set to 0x01.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

num_session can be an 8-bit unsigned integer field that provides thenumber of upper layer sessions carried in the PLP identified by theabove PLP_ID field. When the value of signaling_type field is 0x01, thisfield can indicate the number of UDP/IP sessions in the PLP.

src_IP_add can be a 32-bit unsigned integer field that contains thesource IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_IP_add can be a 32-bit unsigned integer field that contains thedestination IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

src_UDP_port can be a 16-bit unsigned integer field that represents thesource UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_UDP_port can be a 16-bit unsigned integer field that represents thedestination UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

SID_flag can be a 1-bit Boolean field that indicates whether the linklayer packet carrying the upper layer session identified by above 4fields, Src_IP_add, Dst_IP_add, Src_UDP_Port and Dst_UDP_Port, has anSID field in its optional header. When the value of this field is set to0, the link layer packet carrying the upper layer session may not havean SID field in its optional header. When the value of this field is setto 1, the link layer packet carrying the upper layer session can have anSID field in its optional header and the value the SID field can be sameas the following SID field in this table.

compressed_flag can be a 1-bit Boolean field that indicates whether theheader compression is applied the link layer packets carrying the upperlayer session identified by above 4 fields, Src_IP_add, Dst_IP_add,Src_UDP_Port and Dst_UDP_Port. When the value of this field is set to 0,the link layer packet carrying the upper layer session may have a valueof 0x00 of Packet_Type field in its base header. When the value of thisfield is set to 1, the link layer packet carrying the upper layersession may have a value of 0x01 of Packet_Type field in its base headerand the Context_ID field can be present.

SID can be an 8-bit unsigned integer field that indicates sub streamidentifier for the link layer packets carrying the upper layer sessionidentified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port andDst_UDP_Port. This field can be present when the value of SID_flag isequal to 1.

context_id can be an 8-bit field that provides a reference for thecontext id (CID) provided in the ROHC-U description table. This fieldcan be present when the value of compressed_flag is equal to 1.

An example of the RoHC-U description table (tsib14020) according to thepresent invention is illustrated. As described in the foregoing, theRoHC-U adaptation module may generate information related to headercompression.

signaling_type can be an 8-bit field that indicates the type ofsignaling carried by this table. The value of signaling_type field forROHC-U description table (RDT) can be set to “0x02”.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

context_id can be an 8-bit field that indicates the context id (CID) ofthe compressed IP stream. In this system, 8-bit CID can be used forlarge CID.

context_profile can be an 8-bit field that indicates the range ofprotocols used to compress the stream. This field can be omitted.

adaptation_mode can be a 2-bit field that indicates the mode ofadaptation module in this PLP. Adaptation modes have been describedabove.

context_config can be a 2-bit field that indicates the combination ofthe context information. If there is no context information in thistable, this field may be set to “0x0”. If the static_chain( ) ordynamic_chain( ) byte is included in this table, this field may be setto “0x01” or “0x02” respectively. If both of the static_chain( ) anddynamic_chain( ) byte are included in this table, this field may be setto “0x03”.

context length can be an 8-bit field that indicates the length of thestatic chain byte sequence. This field can be omitted.

static_chain_byte ( ) can be a field that conveys the static informationused to initialize the ROHC-U decompressor. The size and structure ofthis field depend on the context profile.

dynamic_chain_byte ( ) can be a field that conveys the dynamicinformation used to initialize the ROHC-U decompressor. The size andstructure of this field depend on the context profile.

The static_chain_byte can be defined as sub-header information of IRpacket. The dynamic_chain_byte can be defined as sub-header informationof IR packet and IR-DYN packet.

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the transmitter side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead reduction part, and/or anencapsulation part. In addition, the link layer on the transmitter sidemay include a scheduler for controlling and scheduling an overalloperation of the link layer and/or input and output parts of the linklayer.

First, signaling information of an upper layer and/or a system parametertsib15010 may be delivered to the link layer. In addition, an IP streamincluding IP packets may be delivered to the link layer from an IP layertsib15110.

As described above, the scheduler tsib15020 may determine and controloperations of several modules included in the link layer. The deliveredsignaling information and/or system parameter tsib15010 may be filtereror used by the scheduler tsib15020. Information, which corresponds to apart of the delivered signaling information and/or system parametertsib15010, necessary for a receiver may be delivered to the link layersignaling part. In addition, information, which corresponds to a part ofthe signaling information, necessary for an operation of the link layermay be delivered to an overhead reduction controller tsib15120 or anencapsulation controller tsib15180.

The link layer signaling part may collect information to be transmittedas a signal in a physical layer, and convert/configure the informationin a form suitable for transmission. The link layer signaling part mayinclude a signaling manager tsib15030, a signaling formatter tsib15040,and/or a buffer for channels tsib15050.

The signaling manager tsib15030 may receive signaling informationdelivered from the scheduler tsib15020 and/or signaling (and/or context)information delivered from the overhead reduction part. The signalingmanager tsib15030 may determine a path for transmission of the signalinginformation for delivered data. The signaling information may bedelivered through the path determined by the signaling managertsib15030. As described in the foregoing, signaling information to betransmitted through a divided channel such as the FIC, the EAS, etc. maybe delivered to the signaling formatter tsib15040, and other signalinginformation may be delivered to an encapsulation buffer tsib15070.

The signaling formatter tsib15040 may format related signalinginformation in a form suitable for each divided channel such thatsignaling information may be transmitted through a separately dividedchannel. As described in the foregoing, the physical layer may includeseparate physically/logically divided channels. The divided channels maybe used to transmit FIC signaling information or EAS-relatedinformation. The FIC or EAS-related information may be sorted by thesignaling manager tsib15030, and input to the signaling formattertsib15040. The signaling formatter tsib15040 may format the informationbased on each separate channel. When the physical layer is designed totransmit particular signaling information through a separately dividedchannel other than the FIC and the EAS, a signaling formatter for theparticular signaling information may be additionally provided. Throughthis scheme, the link layer may be compatible with various physicallayers.

The buffer for channels tsib15050 may deliver the signaling informationreceived from the signaling formatter tsib15040 to separate dedicatedchannels tsib15060. The number and content of the separate channels mayvary depending on embodiments.

As described in the foregoing, the signaling manager tsib15030 maydeliver signaling information, which is not delivered to a particularchannel, to the encapsulation buffer tsib15070. The encapsulation buffertsib15070 may function as a buffer that receives the signalinginformation which is not delivered to the particular channel.

An encapsulation block for signaling information tsib15080 mayencapsulate the signaling information which is not delivered to theparticular channel. A transmission buffer tsib15090 may function as abuffer that delivers the encapsulated signaling information to a DP forsignaling information tsib15100. Here, the DP for signaling informationtsib15100 may refer to the above-described PLS region.

The overhead reduction part may allow efficient transmission by removingoverhead of packets delivered to the link layer. It is possible toconfigure overhead reduction parts corresponding to the number of IPstreams input to the link layer.

An overhead reduction buffer tsib15130 may receive an IP packetdelivered from an upper layer. The received IP packet may be input tothe overhead reduction part through the overhead reduction buffertsib15130.

An overhead reduction controller tsib15120 may determine whether toperform overhead reduction on a packet stream input to the overheadreduction buffer tsib15130. The overhead reduction controller tsib15120may determine whether to perform overhead reduction for each packetstream. When overhead reduction is performed on a packet stream, packetsmay be delivered to a robust header compression (RoHC) compressortsib15140 to perform overhead reduction. When overhead reduction is notperformed on a packet stream, packets may be delivered to theencapsulation part to perform encapsulation without overhead reduction.Whether to perform overhead reduction of packets may be determined basedon the signaling information tsib15010 delivered to the link layer. Thesignaling information may be delivered to the encapsulation controllertsib15180 by the scheduler tsib15020.

The RoHC compressor tsib15140 may perform overhead reduction on a packetstream. The RoHC compressor tsib15140 may perform an operation ofcompressing a header of a packet. Various schemes may be used foroverhead reduction. Overhead reduction may be performed using a schemeproposed by the present invention. The present invention presumes an IPstream, and thus an expression “RoHC compressor” is used. However, thename may be changed depending on embodiments. The operation is notrestricted to compression of the IP stream, and overhead reduction ofall types of packets may be performed by the RoHC compressor tsib15140.

A packet stream configuration block tsib15150 may separate informationto be transmitted to a signaling region and information to betransmitted to a packet stream from IP packets having compressedheaders. The information to be transmitted to the packet stream mayrefer to information to be transmitted to a DP region. The informationto be transmitted to the signaling region may be delivered to asignaling and/or context controller tsib15160. The information to betransmitted to the packet stream may be transmitted to the encapsulationpart.

The signaling and/or context controller tsib15160 may collect signalingand/or context information and deliver the signaling and/or contextinformation to the signaling manager in order to transmit the signalingand/or context information to the signaling region.

The encapsulation part may perform an operation of encapsulating packetsin a form suitable for a delivery to the physical layer. It is possibleto configure encapsulation parts corresponding to the number of IPstreams.

An encapsulation buffer tsib15170 may receive a packet stream forencapsulation. Packets subjected to overhead reduction may be receivedwhen overhead reduction is performed, and an input IP packet may bereceived without change when overhead reduction is not performed.

An encapsulation controller tsib15180 may determine whether toencapsulate an input packet stream. When encapsulation is performed, thepacket stream may be delivered to a segmentation/concatenation blocktsib15190. When encapsulation is not performed, the packet stream may bedelivered to a transmission buffer tsib15230. Whether to encapsulatepackets may be determined based on the signaling information tsib15010delivered to the link layer. The signaling information may be deliveredto the encapsulation controller tsib15180 by the scheduler tsib15020.

In the segmentation/concatenation block tsib15190, the above-describedsegmentation or concatenation operation may be performed on packets. Inother words, when an input IP packet is longer than a link layer packetcorresponding to an output of the link layer, one IP packet may besegmented into several segments to configure a plurality of link layerpacket payloads. On the other hand, when an input IP packet is shorterthan a link layer packet corresponding to an output of the link layer,several IP packets may be concatenated to configure one link layerpacket payload.

A packet configuration table tsib15200 may have configurationinformation of a segmented and/or concatenated link layer packet. Atransmitter and a receiver may have the same information in the packetconfiguration table tsib15200. The transmitter and the receiver mayrefer to the information of the packet configuration table tsib15200. Anindex value of the information of the packet configuration tabletsib15200 may be included in a header of the link layer packet.

A link layer header information block tsib15210 may collect headerinformation generated in an encapsulation process. In addition, the linklayer header information block tsib15210 may collect header informationincluded in the packet configuration table tsib15200. The link layerheader information block tsib15210 may configure header informationaccording to a header structure of the link layer packet.

A header attachment block tsib15220 may add a header to a payload of asegmented and/or concatenated link layer packet. The transmission buffertsib15230 may function as a buffer to deliver the link layer packet to aDP tsib15240 of the physical layer.

The respective blocks, modules, or parts may be configured as onemodule/protocol or a plurality of modules/protocols in the link layer.

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the receiver side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead processing part, and/or adecapsulation part. In addition, the link layer on the receiver side mayinclude a scheduler for controlling and scheduling overall operation ofthe link layer and/or input and output parts of the link layer.

First, information received through a physical layer may be delivered tothe link layer. The link layer may process the information, restore anoriginal state before being processed at a transmitter side, and thendeliver the information to an upper layer. In the present embodiment,the upper layer may be an IP layer.

Information, which is separated in the physical layer and deliveredthrough a particular channel tsib16030, may be delivered to a link layersignaling part. The link layer signaling part may determine signalinginformation received from the physical layer, and deliver the determinedsignaling information to each part of the link layer.

A buffer for channels tsib16040 may function as a buffer that receivessignaling information transmitted through particular channels. Asdescribed in the foregoing, when physically/logically divided separatechannels are present in the physical layer, it is possible to receivesignaling information transmitted through the channels. When theinformation received from the separate channels is segmented, thesegmented information may be stored until complete information isconfigured.

A signaling decoder/parser tsib16050 may verify a format of thesignaling information received through the particular channel, andextract information to be used in the link layer. When the signalinginformation received through the particular channel is encoded, decodingmay be performed. In addition, according to a given embodiment, it ispossible to verify integrity, etc. of the signaling information.

A signaling manager tsib16060 may integrate signaling informationreceived through several paths. Signaling information received through aDP for signaling tsib16070 to be described below may be integrated inthe signaling manager tsib16060. The signaling manager tsib16060 maydeliver signaling information necessary for each part in the link layer.For example, the signaling manager tsib16060 may deliver contextinformation, etc. for recovery of a packet to the overhead processingpart. In addition, the signaling manager tsib16060 may deliver signalinginformation for control to a scheduler tsib16020.

General signaling information, which is not received through a separateparticular channel, may be received through the DP for signalingtsib16070. Here, the DP for signaling may refer to PLS, L1, etc. Here,the DP may be referred to as a PLP. A reception buffer tsib16080 mayfunction as a buffer that receives signaling information delivered fromthe DP for signaling. In a decapsulation block for signaling informationtsib16090, the received signaling information may be decapsulated. Thedecapsulated signaling information may be delivered to the signalingmanager tsib16060 through a decapsulation buffer tsib16100. As describedin the foregoing, the signaling manager tsib16060 may collate signalinginformation, and deliver the collated signaling information to anecessary part in the link layer.

The scheduler tsib16020 may determine and control operations of severalmodules included in the link layer. The scheduler tsib16020 may controleach part of the link layer using receiver information tsib16010 and/orinformation delivered from the signaling manager tsib16060. In addition,the scheduler tsib16020 may determine an operation mode, etc. of eachpart. Here, the receiver information tsib16010 may refer to informationpreviously stored in the receiver. The scheduler tsib16020 may useinformation changed by a user such as channel switching, etc. to performa control operation.

The decapsulation part may filter a packet received from a DP tsib16110of the physical layer, and separate a packet according to a type of thepacket. It is possible to configure decapsulation parts corresponding tothe number of DPs that can be simultaneously decoded in the physicallayer.

The decapsulation buffer tsib16100 may function as a buffer thatreceives a packet stream from the physical layer to performdecapsulation. A decapsulation controller tsib16130 may determinewhether to decapsulate an input packet stream. When decapsulation isperformed, the packet stream may be delivered to a link layer headerparser tsib16140. When decapsulation is not performed, the packet streammay be delivered to an output buffer tsib16220. The signalinginformation received from the scheduler tsib16020 may be used todetermine whether to perform decapsulation.

The link layer header parser tsib16140 may identify a header of thedelivered link layer packet. It is possible to identify a configurationof an IP packet included in a payload of the link layer packet byidentifying the header. For example, the IP packet may be segmented orconcatenated.

A packet configuration table tsib16150 may include payload informationof segmented and/or concatenated link layer packets. The transmitter andthe receiver may have the same information in the packet configurationtable tsib16150. The transmitter and the receiver may refer to theinformation of the packet configuration table tsib16150. It is possibleto find a value necessary for reassembly based on index informationincluded in the link layer packet.

A reassembly block tsib16160 may configure payloads of the segmentedand/or concatenated link layer packets as packets of an original IPstream. Segments may be collected and reconfigured as one IP packet, orconcatenated packets may be separated and reconfigured as a plurality ofIP packet streams. Recombined IP packets may be delivered to theoverhead processing part.

The overhead processing part may perform an operation of restoring apacket subjected to overhead reduction to an original packet as areverse operation of overhead reduction performed in the transmitter.This operation may be referred to as overhead processing. It is possibleto configure overhead processing parts corresponding to the number ofDPs that can be simultaneously decoded in the physical layer.

A packet recovery buffer tsib16170 may function as a buffer thatreceives a decapsulated RoHC packet or IP packet to perform overheadprocessing.

An overhead controller tsib16180 may determine whether to recover and/ordecompress the decapsulated packet. When recovery and/or decompressionare performed, the packet may be delivered to a packet stream recoveryblock tsib16190. When recovery and/or decompression are not performed,the packet may be delivered to the output buffer tsib16220. Whether toperform recovery and/or decompression may be determined based on thesignaling information delivered by the scheduler tsib16020.

The packet stream recovery block tsib16190 may perform an operation ofintegrating a packet stream separated from the transmitter with contextinformation of the packet stream. This operation may be a process ofrestoring a packet stream such that an RoHC decompressor tsib16210 canperform processing. In this process, it is possible to receive signalinginformation and/or context information from a signaling and/or contextcontroller tsib16200. The signaling and/or context controller tsib16200may determine signaling information delivered from the transmitter, anddeliver the signaling information to the packet stream recovery blocktsib16190 such that the signaling information may be mapped to a streamcorresponding to a context ID.

The RoHC decompressor tsib16210 may restore headers of packets of thepacket stream. The packets of the packet stream may be restored to formsof original IP packets through restoration of the headers. In otherwords, the RoHC decompressor tsib16210 may perform overhead processing.

The output buffer tsib16220 may function as a buffer before an outputstream is delivered to an IP layer tsib16230.

The link layers of the transmitter and the receiver proposed in thepresent invention may include the blocks or modules described above. Inthis way, the link layer may independently operate irrespective of anupper layer and a lower layer, overhead reduction may be efficientlyperformed, and a supportable function according to an upper/lower layermay be easily defined/added/deleted.

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides).

In the present invention, a plurality of service providers(broadcasters) may provide services within one frequency band. Inaddition, a service provider may provide a plurality of services, andone service may include one or more components. It can be consideredthat the user receives content using a service as a unit.

The present invention presumes that a transmission protocol based on aplurality of sessions is used to support an IP hybrid broadcast.Signaling information delivered through a signaling path may bedetermined based on a transmission configuration of each protocol.Various names may be applied to respective protocols according to agiven embodiment.

In the illustrated data configuration tsib17010 on the transmittingside, service providers (broadcasters) may provide a plurality ofservices (Service #1, #2, . . . ). In general, a signal for a servicemay be transmitted through a general transmission session (signaling C).However, the signal may be transmitted through a particular session(dedicated session) according to a given embodiment (signaling B).

Service data and service signaling information may be encapsulatedaccording to a transmission protocol. According to a given embodiment,an IP/UDP layer may be used. According to a given embodiment, a signalin the IP/UDP layer (signaling A) may be additionally provided. Thissignaling may be omitted.

Data processed using the IP/UDP may be input to the link layer. Asdescribed in the foregoing, overhead reduction and/or encapsulation maybe performed in the link layer. Here, link layer signaling may beadditionally provided. Link layer signaling may include a systemparameter, etc. Link layer signaling has been described above.

The service data and the signaling information subjected to the aboveprocess may be processed through PLPs in a physical layer. Here, a PLPmay be referred to as a DP. The example illustrated in the figurepresumes a case in which a base DP/PLP is used. However, depending onembodiments, transmission may be performed using only a general DP/PLPwithout the base DP/PLP.

In the example illustrated in the figure, a particular channel(dedicated channel) such as an FIC, an EAC, etc. is used. A signaldelivered through the FIC may be referred to as a fast information table(FIT), and a signal delivered through the EAC may be referred to as anemergency alert table (EAT). The FIT may be identical to theabove-described SLT. The particular channels may not be used dependingon embodiments. When the particular channel (dedicated channel) is notconfigured, the FIT and the EAT may be transmitted using a general linklayer signaling transmission scheme, or transmitted using a PLP via theIP/UDP as other service data.

According to a given embodiment, system parameters may include atransmitter-related parameter, a service provider-related parameter,etc. Link layer signaling may include IP header compression-relatedcontext information and/or identification information of data to whichthe context is applied. Signaling of an upper layer may include an IPaddress, a UDP number, service/component information, emergencyalert-related information, an IP/UDP address for service signaling, asession ID, etc. Detailed examples thereof have been described above.

In the illustrated data configuration tsib17020 on the receiving side,the receiver may decode only a PLP for a corresponding service usingsignaling information without having to decode all PLPs.

First, when the user selects or changes a service desired to bereceived, the receiver may be tuned to a corresponding frequency and mayread receiver information related to a corresponding channel stored in aDB, etc. The information stored in the DB, etc. of the receiver may beconfigured by reading an SLT at the time of initial channel scan.

After receiving the SLT and the information about the correspondingchannel, information previously stored in the DB is updated, andinformation about a transmission path of the service selected by theuser and information about a path, through which component informationis acquired or a signal necessary to acquire the information istransmitted, are acquired. When the information is not determined to bechanged using version information of the SLT, decoding or parsing may beomitted.

The receiver may verify whether SLT information is included in a PLP byparsing physical signaling of the PLP in a corresponding broadcaststream (not illustrated), which may be indicated through a particularfield of physical signaling. It is possible to access a position atwhich a service layer signal of a particular service is transmitted byaccessing the SLT information. The service layer signal may beencapsulated into the IP/UDP and delivered through a transmissionsession. It is possible to acquire information about a componentincluded in the service using this service layer signaling. A specificSLT-SLS configuration is as described above.

In other words, it is possible to acquire transmission path information,for receiving upper layer signaling information (service signalinginformation) necessary to receive the service, corresponding to one ofseveral packet streams and PLPs currently transmitted on a channel usingthe SLT. The transmission path information may include an IP address, aUDP port number, a session ID, a PLP ID, etc. Here, depending onembodiments, a value previously designated by the IANA or a system maybe used as an IP/UDP address. The information may be acquired using ascheme of accessing a DB or a shared memory, etc.

When the link layer signal and service data are transmitted through thesame PLP, or only one PLP is operated, service data delivered throughthe PLP may be temporarily stored in a device such as a buffer, etc.while the link layer signal is decoded.

It is possible to acquire information about a path through which theservice is actually transmitted using service signaling information of aservice to be received. In addition, a received packet stream may besubjected to decapsulation and header recovery using information such asoverhead reduction for a PLP to be received, etc.

In the illustrated example (tsib17020), the FIC and the EAC are used,and a concept of the base DP/PLP is presumed. As described in theforegoing, concepts of the FIC, the EAC, and the base DP/PLP may not beused.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas. The present invention proposes a physical profile (orsystem) optimized to minimize receiver complexity while attaining theperformance required for a particular use case. Physical (PHY) profiles(base, handheld and advanced profiles) according to an embodiment of thepresent invention are subsets of all configurations that a correspondingreceiver should implement. The PHY profiles share most of the functionalblocks but differ slightly in specific blocks and/or parameters. For thesystem evolution, future profiles may also be multiplexed with existingprofiles in a single radio frequency (RF) channel through a futureextension frame (FEF). The base profile and the handheld profileaccording to the embodiment of the present invention refer to profilesto which MIMO is not applied, and the advanced profile refers to aprofile to which MIMO is applied. The base profile may be used as aprofile for both the terrestrial broadcast service and the mobilebroadcast service. That is, the base profile may be used to define aconcept of a profile which includes the mobile profile. In addition, theadvanced profile may be divided into an advanced profile for a baseprofile with MIMO and an advanced profile for a handheld profile withMIMO. Moreover, the profiles may be changed according to intention ofthe designer.

The following terms and definitions may be applied to the presentinvention. The following terms and definitions may be changed accordingto design.

Auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators

Base data pipe: data pipe that carries service signaling data

Baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding)

Cell: modulation value that is carried by one carrier of orthogonalfrequency division multiplexing (OFDM) transmission

Coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data

Data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or a plurality ofservice(s) or service component(s).

Data pipe unit (DPU): a basic unit for allocating data cells to a DP ina frame.

Data symbol: OFDM symbol in a frame which is not a preamble symbol (thedata symbol encompasses the frame signaling symbol and frame edgesymbol)

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID

Dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams

Emergency alert channel (EAC): part of a frame that carries EASinformation data

Frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol

Frame repetition unit: a set of frames belonging to the same ordifferent physical layer profiles including an FEF, which is repeatedeight times in a superframe

Fast information channel (FIC): a logical channel in a frame thatcarries mapping information between a service and the corresponding baseDP

FECBLOCK: set of LDPC-encoded bits of DP data

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of an elementary period T

Frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data

Frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern

Frame group: the set of all frames having the same PHY profile type in asuperframe

Future extension frame: physical layer time slot within the superframethat may be used for future extension, which starts with a preamble

Futurecast UTB system: proposed physical layer broadcast system, theinput of which is one or more MPEG2-TS, IP or general stream(s) and theoutput of which is an RF signal

Input stream: a stream of data for an ensemble of services delivered tothe end users by the system

Normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol

PHY profile: subset of all configurations that a corresponding receivershould implement

PLS: physical layer signaling data including PLS1 and PLS2

PLS1: a first set of PLS data carried in a frame signaling symbol (FSS)having a fixed size, coding and modulation, which carries basicinformation about a system as well as parameters needed to decode PLS2

NOTE: PLS1 data remains constant for the duration of a frame group

PLS2: a second set of PLS data transmitted in the FSS, which carriesmore detailed PLS data about the system and the DPs

PLS2 dynamic data: PLS2 data that dynamically changes frame-by-frame

PLS2 static data: PLS2 data that remains static for the duration of aframe group

Preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system

Preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located at the beginning of a frame

The preamble symbol is mainly used for fast initial band scan to detectthe system signal, timing thereof, frequency offset, and FFT size.

Reserved for future use: not defined by the present document but may bedefined in future

Superframe: set of eight frame repetition units

Time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of a timeinterleaver memory

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs

NOTE: The TI group may be mapped directly to one frame or may be mappedto a plurality of frames. The TI group may contain one or more TIblocks.

Type 1 DP: DP of a frame where all DPs are mapped to the frame in timedivision multiplexing (TDM) scheme

Type 2 DP: DP of a frame where all DPs are mapped to the frame infrequency division multiplexing (FDM) scheme

XFECBLOCK: set of Ncells cells carrying all the bits of one LDPCFECBLOCK

FIG. 18 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal transmission apparatus for future broadcastservices according to the present embodiment may include an inputformatting block 1000, a bit interleaved coding & modulation (BICM)block 1010, a frame building block 1020, an OFDM generation block 1030and a signaling generation block 1040. Description will be given of anoperation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IPstream/packets and MPEG2-TS may be main input formats, and other streamtypes are handled as general streams. In addition to these data inputs,management information is input to control scheduling and allocation ofthe corresponding bandwidth for each input stream. In addition, thepresent invention allows simultaneous input of one or a plurality of TSstreams, IP stream(s) and/or a general stream(s).

The input formatting block 1000 may demultiplex each input stream intoone or a plurality of data pipes, to each of which independent codingand modulation are applied. A DP is the basic unit for robustnesscontrol, which affects QoS. One or a plurality of services or servicecomponents may be carried by one DP. The DP is a logical channel in aphysical layer for delivering service data or related metadata capableof carrying one or a plurality of services or service components.

In addition, a DPU is a basic unit for allocating data cells to a DP inone frame.

An input to the physical layer may include one or a plurality of datastreams. Each of the data streams is delivered by one DP. The inputformatting block 1000 may covert a data stream input through one or morephysical paths (or DPs) into a baseband frame (BBF). In this case, theinput formatting block 1000 may perform null packet deletion or headercompression on input data (a TS or IP input stream) in order to enhancetransmission efficiency. A receiver may have a priori information for aparticular part of a header, and thus this known information may bedeleted from a transmitter. A null packet deletion block 3030 may beused only for a TS input stream.

In the BICM block 1010, parity data is added for error correction andencoded bit streams are mapped to complex-value constellation symbols.The symbols are interleaved across a specific interleaving depth that isused for the corresponding DP. For the advanced profile, MIMO encodingis performed in the BICM block 1010 and an additional data path is addedat the output for MIMO transmission.

The frame building block 1020 may map the data cells of the input DPsinto the OFDM symbols within a frame, and perform frequency interleavingfor frequency-domain diversity, especially to combat frequency-selectivefading channels. The frame building block 1020 may include a delaycompensation block, a cell mapper and a frequency interleaver.

The delay compensation block may adjust timing between DPs andcorresponding PLS data to ensure that the DPs and the corresponding PLSdata are co-timed at a transmitter side. The PLS data is delayed by thesame amount as the data pipes by addressing the delays of data pipescaused by the input formatting block and BICM block. The delay of theBICM block is mainly due to the time interleaver. In-band signaling datacarries information of the next TI group so that the information iscarried one frame ahead of the DPs to be signaled. The delaycompensation block delays in-band signaling data accordingly.

The cell mapper may map PLS, DPs, auxiliary streams, dummy cells, etc.to active carriers of the OFDM symbols in the frame. The basic functionof the cell mapper 7010 is to map data cells produced by the TIs foreach of the DPs, PLS cells, and EAC/FIC cells, if any, into arrays ofactive OFDM cells corresponding to each of the OFDM symbols within aframe. A basic function of the cell mapper is to map a data cellgenerated by time interleaving for each DP and PLS cell to an array ofactive OFDM cells (if present) corresponding to respective OFDM symbolsin one frame. Service signaling data (such as program specificinformation (PSI)/SI) may be separately gathered and sent by a DP. Thecell mapper operates according to dynamic information produced by ascheduler and the configuration of a frame structure. The frequencyinterleaver may randomly interleave data cells received from the cellmapper to provide frequency diversity. In addition, the frequencyinterleaver may operate on an OFDM symbol pair including two sequentialOFDM symbols using a different interleaving-seed order to obtain maximuminterleaving gain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells producedby the frame building block, inserts pilots, and produces a time domainsignal for transmission. In addition, this block subsequently insertsguard intervals, and applies peak-to-average power ratio (PAPR)reduction processing to produce a final RF signal.

Specifically, after inserting a preamble at the beginning of each frame,the OFDM generation block 1030 may apply conventional OFDM modulationhaving a cyclic prefix as a guard interval. For antenna space diversity,a distributed MISO scheme is applied across transmitters. In addition, aPAPR scheme is performed in the time domain. For flexible networkplanning, the present invention provides a set of various FFT sizes,guard interval lengths and corresponding pilot patterns.

In addition, the present invention may multiplex signals of a pluralityof broadcast transmission/reception systems in the time domain such thatdata of two or more different broadcast transmission/reception systemsproviding broadcast services may be simultaneously transmitted in thesame RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

The signaling generation block 1040 may create physical layer signalinginformation used for an operation of each functional block. Thissignaling information is also transmitted so that services of interestare properly recovered at a receiver side. Signaling informationaccording to an embodiment of the present invention may include PLSdata. PLS provides the receiver with a means to access physical layerDPs. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in aframe having a fixed size, coding and modulation, which carries basicinformation about the system in addition to the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable reception anddecoding of the PLS2 data. In addition, the PLS1 data remains constantfor the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode a desired DP. The PLS2 signaling further includes twotypes of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamicdata (PLS2-DYN data). The PLS2 static data is PLS2 data that remainsstatic for the duration of a frame group and the PLS2 dynamic data isPLS2 data that dynamically changes frame by frame. Details of the PLSdata will be described later.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 19 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 19 corresponds to an embodiment ofthe BICM block 1010 described with reference to FIG. 18.

As described above, the broadcast signal transmission apparatus forfuture broadcast services according to the embodiment of the presentinvention may provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS depends on characteristics of a service provided by thebroadcast signal transmission apparatus for future broadcast servicesaccording to the embodiment of the present invention, data correspondingto respective services needs to be processed using different schemes.Accordingly, the BICM block according to the embodiment of the presentinvention may independently process respective DPs by independentlyapplying SISO, MISO and MIMO schemes to data pipes respectivelycorresponding to data paths. Consequently, the broadcast signaltransmission apparatus for future broadcast services according to theembodiment of the present invention may control QoS for each service orservice component transmitted through each DP.

(a) shows a BICM block applied to a profile (or system) to which MIMO isnot applied, and (b) shows a BICM block of a profile (or system) towhich MIMO is applied.

The BICM block to which MIMO is not applied and the BICM block to whichMIMO is applied may include a plurality of processing blocks forprocessing each DP.

Description will be given of each processing block of the BICM block towhich MIMO is not applied and the BICM block to which MIMO is applied.

A processing block 5000 of the BICM block to which MIMO is not appliedmay include a data FEC encoder 5010, a bit interleaver 5020, aconstellation mapper 5030, a signal space diversity (SSD) encoding block5040 and a time interleaver 5050.

The data FEC encoder 5010 performs FEC encoding on an input BBF togenerate FECBLOCK procedure using outer coding (BCH) and inner coding(LDPC). The outer coding (BCH) is optional coding method. A detailedoperation of the data FEC encoder 5010 will be described later.

The bit interleaver 5020 may interleave outputs of the data FEC encoder5010 to achieve optimized performance with a combination of LDPC codesand a modulation scheme while providing an efficiently implementablestructure. A detailed operation of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 may modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or each cellword from the cell-word demultiplexer 5010-1 in the advanced profileusing either QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, orNUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, orNUC-1024) mapping to give a power-normalized constellation point, el.This constellation mapping is applied only for DPs. It is observed thatQAM-16 and NUQs are square shaped, while NUCs have arbitrary shapes.When each constellation is rotated by any multiple of 90 degrees, therotated constellation exactly overlaps with its original one. This“rotation-sense” symmetric property makes the capacities and the averagepowers of the real and imaginary components equal to each other. BothNUQs and NUCs are defined specifically for each code rate and theparticular one used is signaled by the parameter DP_MOD filed in thePLS2 data.

The time interleaver 5050 may operates at a DP level. Parameters of timeinterleaving (TI) may be set differently for each DP. A detailedoperation of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block to which MIMO is applied mayinclude the data FEC encoder, the bit interleaver, the constellationmapper, and the time interleaver.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 of the BICM block to which MIMO is not applied inthat the processing block 5000-1 further includes a cell-worddemultiplexer 5010-1 and a MIMO encoding block 5020-1.

In addition, operations of the data FEC encoder, the bit interleaver,the constellation mapper, and the time interleaver in the processingblock 5000-1 correspond to those of the data FEC encoder 5010, the bitinterleaver 5020, the constellation mapper 5030, and the timeinterleaver 5050 described above, and thus description thereof isomitted.

The cell-word demultiplexer 5010-1 is used for a DP of the advancedprofile to divide a single cell-word stream into dual cell-word streamsfor MIMO processing.

The MIMO encoding block 5020-1 may process an output of the cell-worddemultiplexer 5010-1 using a MIMO encoding scheme. The MIMO encodingscheme is optimized for broadcast signal transmission. MIMO technologyis a promising way to obtain a capacity increase but depends on channelcharacteristics. Especially for broadcasting, a strong LOS component ofa channel or a difference in received signal power between two antennascaused by different signal propagation characteristics makes itdifficult to obtain capacity gain from MIMO. The proposed MIMO encodingscheme overcomes this problem using rotation-based precoding and phaserandomization of one of MIMO output signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. A MIMO encoding modeof the present invention may be defined as full-rate spatialmultiplexing (FR-SM). FR-SM encoding may provide capacity increase withrelatively small complexity increase at the receiver side. In addition,the MIMO encoding scheme of the present invention has no restriction onan antenna polarity configuration.

MIMO processing is applied at the DP level. NUQ (e1,i and e2,i)corresponding to a pair of constellation mapper outputs is fed to aninput of a MIMO encoder. Paired MIMO encoder output (g1,i and g2,i) istransmitted by the same carrier k and OFDM symbol I of respective TXantennas thereof.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 20 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 20 corresponds to another embodimentof the BICM block 1010 described with reference to FIG. 18.

FIG. 20 illustrates a BICM block for protection of physical layersignaling (PLS), an emergency alert channel (EAC) and a fast informationchannel (FIC). The EAC is a part of a frame that carries EAS informationdata, and the FIC is a logical channel in a frame that carries mappinginformation between a service and a corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 20, the BICM block for protection of the PLS, the EACand the FIC may include a PLS FEC encoder 6000, a bit interleaver 6010and a constellation mapper 6020.

In addition, the PLS FEC encoder 6000 may include a scrambler, a BCHencoding/zero insertion block, an LDPC encoding block and an LDPC paritypunturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 may encode scrambled PLS 1/2 data, EAC and FICsections.

The scrambler may scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block may perform outer encoding on thescrambled PLS 1/2 data using a shortened BCH code for PLS protection,and insert zero bits after BCH encoding. For PLS1 data only, output bitsof zero insertion may be permutted before LDPC encoding.

The LDPC encoding block may encode an output of the BCH encoding/zeroinsertion block using an LDPC code. To generate a complete coded block,Cldpc and parity bits Pldpc are encoded systematically from eachzero-inserted PLS information block Ildpc and appended thereto.

$\begin{matrix}{C_{ldpc} = {\lbrack {I_{ldpc}\mspace{14mu} P_{ldpc}} \rbrack = \lbrack {i_{0},i_{1},\ldots\;,i_{K_{ldpc} - 1},p_{0},p_{1},\ldots\;,p_{N_{ldpc} - K_{ldpc} - 1}} \rbrack}} & \lbrack {{Equation}\mspace{14mu} 1} \rbrack\end{matrix}$

The LDPC parity punturing block may perform puncturing on the PLS1 dataand the PLS2 data.

When shortening is applied to PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. In addition, for PLS2 dataprotection, LDPC parity bits of PLS2 are punctured after LDPC encoding.These punctured bits are not transmitted.

The bit interleaver 6010 may interleave each of shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 may map the bit-interleaved PLS1 data andPLS2 data to constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 21 illustrates a bit interleaving process of PLS according to anembodiment of the present invention.

Each shortened and punctured PLS1 and PLS2 coded block is interleavedbit-by-bit as described in FIG. 22. Each block of additional parity bitsis interleaved with the same block interleaving structure butseparately.

In the case of BPSK, there are two branches for bit interleaving toduplicate FEC coded bits in the real and imaginary parts. Each codedblock is written to the upper branch first. The bits are mapped to thelower branch by applying modulo NFEC addition with cyclic shifting valuefloor(NFEC/2), where NFEC is the length of each LDPC coded block aftershortening and puncturing.

In other modulation cases, such as QSPK, QAM-16 and NUQ-64, FEC codedbits are written serially into the interleaver column-wise, where thenumber of columns is the same as the modulation order.

In the read operation, the bits for one constellation symbol are readout sequentially row-wise and fed into the bit demultiplexer block.These operations are continued until the end of the column.

Each bit interleaved group is demultiplexed bit-by-bit in a group beforeconstellation mapping. Depending on modulation order, there are twomapping rules. In the case of BPSK and QPSK, the reliability of bits ina symbol is equal. Therefore, the bit group read out from the bitinterleaving block is mapped to a QAM symbol without any operation.

In the cases of QAM-16 and NUQ-64 mapped to a QAM symbol, the rule ofoperation is described in FIG. 23(a). As shown in FIG. 23(a), i is bitgroup index corresponding to column index in bit interleaving.

FIG. 21 shows the bit demultiplexing rule for QAM-16. This operationcontinues until all bit groups are read from the bit interleaving block.

FIG. 22 illustrates a configuration of a broadcast signal receptionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may correspond tothe broadcast signal transmission apparatus for future broadcastservices described with reference to FIG. 18.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may include asynchronization & demodulation module 9000, a frame parsing module 9010,a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the broadcast signal reception apparatus.

The synchronization & demodulation module 9000 may receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the broadcast signal receptionapparatus, and carry out demodulation corresponding to a reverseprocedure of a procedure performed by the broadcast signal transmissionapparatus.

The frame parsing module 9010 may parse input signal frames and extractdata through which a service selected by a user is transmitted. If thebroadcast signal transmission apparatus performs interleaving, the frameparsing module 9010 may carry out deinterleaving corresponding to areverse procedure of interleaving. In this case, positions of a signaland data that need to be extracted may be obtained by decoding dataoutput from the signaling decoding module 9040 to restore schedulinginformation generated by the broadcast signal transmission apparatus.

The demapping & decoding module 9020 may convert input signals into bitdomain data and then deinterleave the same as necessary. The demapping &decoding module 9020 may perform demapping of mapping applied fortransmission efficiency and correct an error generated on a transmissionchannel through decoding. In this case, the demapping & decoding module9020 may obtain transmission parameters necessary for demapping anddecoding by decoding data output from the signaling decoding module9040.

The output processor 9030 may perform reverse procedures of variouscompression/signal processing procedures which are applied by thebroadcast signal transmission apparatus to improve transmissionefficiency. In this case, the output processor 9030 may acquirenecessary control information from data output from the signalingdecoding module 9040. An output of the output processor 9030 correspondsto a signal input to the broadcast signal transmission apparatus and maybe MPEG-TSs, IP streams (v4 or v6) and generic streams.

The signaling decoding module 9040 may obtain PLS information from asignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, the demapping & decodingmodule 9020 and the output processor 9030 may execute functions thereofusing data output from the signaling decoding module 9040.

A frame according to an embodiment of the present invention is furtherdivided into a number of OFDM symbols and a preamble. As shown in (d),the frame includes a preamble, one or more frame signaling symbols(FSSs), normal data symbols and a frame edge symbol (FES).

The preamble is a special symbol that enables fast futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of a signal. Details of thepreamble will be described later.

A main purpose of the FSS is to carry PLS data. For fast synchronizationand channel estimation, and hence fast decoding of PLS data, the FSS hasa dense pilot pattern than a normal data symbol. The FES has exactly thesame pilots as the FSS, which enables frequency-only interpolationwithin the FES and temporal interpolation, without extrapolation, forsymbols immediately preceding the FES.

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention.

FIG. 23 illustrates the signaling hierarchy structure, which is splitinto three main parts corresponding to preamble signaling data 11000,PLS1 data 11010 and PLS2 data 11020. A purpose of a preamble, which iscarried by a preamble symbol in every frame, is to indicate atransmission type and basic transmission parameters of the frame. PLS1enables the receiver to access and decode the PLS2 data, which containsthe parameters to access a DP of interest. PLS2 is carried in everyframe and split into two main parts corresponding to PLS2-STAT data andPLS2-DYN data. Static and dynamic portions of PLS2 data are followed bypadding, if necessary.

Preamble signaling data according to an embodiment of the presentinvention carries 21 bits of information that are needed to enable thereceiver to access PLS data and trace DPs within the frame structure.Details of the preamble signaling data are as follows.

FFT_SIZE: This 2-bit field indicates an FFT size of a current framewithin a frame group as described in the following Table 1.

TABLE 1 Value FFT size 00 8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3-bit field indicates a guard interval fraction valuein a current superframe as described in the following Table 2.

TABLE 2 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80101  1/160 110 to 111 Reserved

EAC_FLAG: This 1-bit field indicates whether the EAC is provided in acurrent frame. If this field is set to ‘1’, an emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, theEAS is not carried in the current frame. This field may be switcheddynamically within a superframe.

PILOT_MODE: This 1-bit field indicates whether a pilot mode is a mobilemode or a fixed mode for a current frame in a current frame group. Ifthis field is set to ‘0’, the mobile pilot mode is used. If the field isset to ‘1’, the fixed pilot mode is used.

PAPR FLAG: This 1-bit field indicates whether PAPR reduction is used fora current frame in a current frame group. If this field is set to avalue of ‘1’, tone reservation is used for PAPR reduction. If this fieldis set to a value of ‘0’, PAPR reduction is not used.

RESERVED: This 7-bit field is reserved for future use.

FIG. 24 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable reception and decoding of PLS2. As mentioned above,the PLS1 data remain unchanged for the entire duration of one framegroup. A detailed definition of the signaling fields of the PLS1 data isas follows.

PREAMBLE_DATA: This 20-bit field is a copy of preamble signaling dataexcluding EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates a format of payload datacarried in a frame group. PAYLOAD_TYPE is signaled as shown in Table 3.

TABLE 3 Value Payload type 1XX TS is transmitted. X1X IP stream istransmitted. XX1 GS is transmitted.

NUM_FSS: This 2-bit field indicates the number of FSSs in a currentframe.

SYSTEM_VERSION: This 8-bit field indicates a version of a transmittedsignal format. SYSTEM_VERSION is divided into two 4-bit fields: a majorversion and a minor version.

Major version: The MSB corresponding to four bits of the SYSTEM_VERSIONfield indicate major version information. A change in the major versionfield indicates a non-backward-compatible change. A default value is‘0000’. For a version described in this standard, a value is set to‘0000’.

Minor version: The LSB corresponding to four bits of SYSTEM_VERSIONfield indicate minor version information. A change in the minor versionfield is backwards compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may include one ormore frequencies depending on the number of frequencies used perfuturecast UTB system. If a value of CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies a currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the futurecast UTBsystem within the ATSC network. The futurecast UTB system is aterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same futurecastUTB system may carry different input streams and use different RFs indifferent geographical areas, allowing local service insertion. Theframe structure and scheduling are controlled in one place and areidentical for all transmissions within the futurecast UTB system. One ormore futurecast UTB systems may have the same SYSTEM_ID meaning thatthey all have the same physical layer structure and configuration.

The following loop includes FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate an FRUconfiguration and a length of each frame type. A loop size is fixed sothat four PHY profiles (including an FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, unused fields are filled with zeros.

FRU_PHY_PROFILE: This 3-bit field indicates a PHY profile type of an(i+1)th (i is a loop index) frame of an associated FRU. This field usesthe same signaling format as shown in Table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates a length of an (i+1)thframe of an associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, an exact value of a frame duration may be obtained.

FRU_GI_FRACTION: This 3-bit field indicates a guard interval fractionvalue of an (i+1)th frame of an associated FRU. FRU_GI_FRACTION issignaled according to Table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates an FEC type used by PLS2protection. The FEC type is signaled according to Table 4. Details ofLDPC codes will be described later.

TABLE 4 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01 to 11Reserved

PLS2_MOD: This 3-bit field indicates a modulation type used by PLS2. Themodulation type is signaled according to Table 5.

TABLE 5 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100 to111 Reserved

PLS2_SIZE_CELL: This 15-bit field indicates Ctotal_partial block, a size(specified as the number of QAM cells) of the collection of full codedblocks for PLS2 that is carried in a current frame group. This value isconstant during the entire duration of the current frame group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-STAT for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-DYN for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_REP_FLAG: This 1-bit flag indicates whether a PLS2 repetition modeis used in a current frame group. When this field is set to a value of‘1’, the PLS2 repetition mode is activated. When this field is set to avalue of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates Ctotal_partial_block, asize (specified as the number of QAM cells) of the collection of partialcoded blocks for PLS2 carried in every frame of a current frame group,when PLS2 repetition is used. If repetition is not used, a value of thisfield is equal to 0. This value is constant during the entire durationof the current frame group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates an FEC type used for PLS2that is carried in every frame of a next frame group. The FEC type issignaled according to Table 10.

PLS2_NEXT_MOD: This 3-bit field indicates a modulation type used forPLS2 that is carried in every frame of a next frame group. Themodulation type is signaled according to Table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in a next frame group. When this field is set toa value of ‘1’, the PLS2 repetition mode is activated. When this fieldis set to a value of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates Ctotal_full_block,a size (specified as the number of QAM cells) of the collection of fullcoded blocks for PLS2 that is carried in every frame of a next framegroup, when PLS2 repetition is used. If repetition is not used in thenext frame group, a value of this field is equal to 0. This value isconstant during the entire duration of a current frame group.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates a size, inbits, of PLS2-STAT for a next frame group. This value is constant in acurrent frame group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for a next frame group. This value is constant ina current frame group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in a current frame group. This value is constantduring the entire duration of the current frame group. Table 6 belowprovides values of this field. When this field is set to a value of‘00’, additional parity is not used for the PLS2 in the current framegroup.

TABLE 6 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10 to 11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates a size (specified as thenumber of QAM cells) of additional parity bits of PLS2. This value isconstant during the entire duration of a current frame group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of a next frame group.This value is constant during the entire duration of a current framegroup. Table 12 defines values of this field.

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates a size (specified asthe number of QAM cells) of additional parity bits of PLS2 in everyframe of a next frame group. This value is constant during the entireduration of a current frame group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to all PLS1signaling.

FIG. 25 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 25 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT datais the same within a frame group, while PLS2-DYN data providesinformation that is specific for a current frame.

Details of fields of the PLS2-STAT data are described below.

FIC_FLAG: This 1-bit field indicates whether the FIC is used in acurrent frame group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofa current frame group.

AUX_FLAG: This 1-bit field indicates whether an auxiliary stream is usedin a current frame group. If this field is set to ‘1’, the auxiliarystream is provided in a current frame. If this field set to ‘0’, theauxiliary stream is not carried in the current frame. This value isconstant during the entire duration of current frame group.

NUM_DP: This 6-bit field indicates the number of DPs carried within acurrent frame. A value of this field ranges from 1 to 64, and the numberof DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates a type of a DP. This is signaledaccording to the following Table 7.

TABLE 7 Value DP Type 000 DP Type 1 001 DP Type 2 010 to 111 Reserved

DP_GROUP_ID: This 8-bit field identifies a DP group with which a currentDP is associated. This may be used by the receiver to access DPs ofservice components associated with a particular service having the sameDP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates a DP carrying service signalingdata (such as PSI/SI) used in a management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with service data or a dedicated DP carrying only the servicesignaling data.

DP_FEC_TYPE: This 2-bit field indicates an FEC type used by anassociated DP. The FEC type is signaled according to the following Table8.

TABLE 8 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10 to 11 Reserved

DP_COD: This 4-bit field indicates a code rate used by an associated OP.The code rate is signaled according to the following Table 9.

TABLE 9 Value Code rate 0000  5/15 0001  6/15 0010  7/15 0011  8/15 0100 9/15 0101 10/15 0110 11/15 0111 12/15 1000 13/15 1001 to 1111 Reserved

DP_MOD: This 4-bit field indicates modulation used by an associated DP.The modulation is signaled according to the following Table 10.

TABLE 10 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-1024 1001 to1111 Reserved

DP_SSD_FLAG: This 1-bit field indicates whether an SSD mode is used inan associated DP. If this field is set to a value of ‘1’, SSD is used.If this field is set to a value of ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to an associated DP. A type of MIMO encoding process issignaled according to the following Table 11.

TABLE 11 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010 to 111 Reserved

DP_TI_TYPE: This 1-bit field indicates a type of time interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI block.

DP_TI_LENGTH: The use of this 2-bit field (allowed values are only 1, 2,4, and 8) is determined by values set within the DP_TI_TYPE field asfollows.

If DP_TI_TYPE is set to a value of ‘1’, this field indicates PI, thenumber of frames to which each TI group is mapped, and one TI block ispresent per TI group (NTI=1). Allowed values of PI with the 2-bit fieldare defined in Table 12 below.

If DP_TI_TYPE is set to a value of ‘0’, this field indicates the numberof TI blocks NTI per TI group, and one TI group is present per frame(PI=1). Allowed values of PI with the 2-bit field are defined in thefollowing Table 12.

TABLE 12 2-bit field PI NTI 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates a frame interval (IJUMP)within a frame group for an associated DP and allowed values are 1, 2,4, and 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’, or ‘11’,respectively). For DPs that do not appear every frame of the framegroup, a value of this field is equal to an interval between successiveframes. For example, if a DP appears on frames 1, 5, 9, 13, etc., thisfield is set to a value of ‘4’. For DPs that appear in every frame, thisfield is set to a value of ‘1’.

DP_TI_BYPASS: This 1-bit field determines availability of the timeinterleaver 5050. If time interleaving is not used for a DP, a value ofthis field is set to ‘1’. If time interleaving is used, the value is setto ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates an index of a first frameof a superframe in which a current DP occurs. A value ofDP_FIRST_FRAME_IDX ranges from 0 to 31.

DP_NUM_BLOCK_MAX: This 10-bit field indicates a maximum value ofDP_NUM_BLOCKS for this DP. A value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates a type of payload datacarried by a given DP. DP_PAYLOAD_TYPE is signaled according to thefollowing Table 13.

TABLE 13 Value Payload type 00 TS 01 IP 10 GS 11 Reserved

DP_INBAND_MODE: This 2-bit field indicates whether a current DP carriesin-band signaling information. An in-band signaling type is signaledaccording to the following Table 14.

TABLE 14 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried 10 INBAND-ISSY is carried 11 INBAND-PLS andINBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates a protocol type of apayload carried by a given DP. The protocol type is signaled accordingto Table 15 below when input payload types are selected.

TABLE 15 If If If DP_PAY- DP_PAY- DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue is TS is IP is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inan input formatting block. A CRC mode is signaled according to thefollowing Table 16.

TABLE 16 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates a null-packet deletion mode used byan associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODE issignaled according to Table 17 below. If DP_PAYLOAD_TYPE is not TS(‘00’), DNP_MODE is set to a value of ‘00’.

TABLE 17 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 Reserved

ISSY_MODE: This 2-bit field indicates an ISSY mode used by an associatedDP when DP_PAYLOAD_TYPE is set to TS (‘00’). ISSY_MODE is signaledaccording to Table 18 below. If DP_PAYLOAD_TYPE is not TS (‘00’),ISSY_MODE is set to the value of ‘00’.

TABLE 18 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 Reserved

HC_MODE_TS: This 2-bit field indicates a TS header compression mode usedby an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). HC_MODE TSis signaled according to the following Table 19.

TABLE 19 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates an IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). HC_MODE_IP is signaledaccording to the following Table 20.

TABLE 20 Value Header compression mode 00 No compression 01 HC_MODE_IP 110 to 11 Reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if FIC_FLAG is equal to ‘1’.

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if AUX_FLAG is equal to ‘1’.

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary stream is used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicating atype of a current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 26 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 26 illustrates PLS2-DYN data of the PLS2 data. Values of thePLS2-DYN data may change during the duration of one frame group whilesizes of fields remain constant.

Details of fields of the PLS2-DYN data are as below.

FRAME_INDEX: This 5-bit field indicates a frame index of a current framewithin a superframe. An index of a first frame of the superframe is setto ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration changes. A next superframe with changes in theconfiguration is indicated by a value signaled within this field. Ifthis field is set to a value of ‘0000’, it means that no scheduledchange is foreseen. For example, a value of ‘1’ indicates that there isa change in the next superframe.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration (i.e., content of the FIC) changes. A nextsuperframe with changes in the configuration is indicated by a valuesignaled within this field. If this field is set to a value of ‘0000’,it means that no scheduled change is foreseen. For example, a value of‘0001’ indicates that there is a change in the next superframe.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in a loop over NUM_DP, which describeparameters associated with a DP carried in a current frame.

DP_ID: This 6-bit field uniquely indicates a DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates a start position ofthe first of the DPs using a DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the following Table 21.

TABLE 21 DP_START field size PHY profile 64K 16K Base 13 bits 15 bitsHandheld — 13 bits Advanced 13 bits its

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in acurrent TI group for a current DP. A value of DP_NUM_BLOCK ranges from 0to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate FIC parameters associated with the EAC.

EAC_FLAG: This 1-bit field indicates the presence of the EAC in acurrent frame. This bit is the same value as EAC_FLAG in a preamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates a version number ofa wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated to EAC_LENGTH_BYTE.

If the EAC_FLAG field is equal to ‘0’, the following 12 bits areallocated to EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates a length, in bytes, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of frames before aframe where the EAC arrives.

The following fields appear only if the AUX_FLAG field is equal to ‘1’.

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. A meaning of this field depends on a valueof AUX_STREAM_TYPE in a configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped to the active carriers of OFDM symbols in a frame. PLS1and PLS2 are first mapped to one or more FSSs. Thereafter, EAC cells, ifany, are mapped to an immediately following PLS field, followed next byFIC cells, if any. The DPs are mapped next after the PLS or after theEAC or the FIC, if any. Type 1 DPs are mapped first and Type 2 DPs aremapped next. Details of types of the DPs will be described later. Insome cases, DPs may carry some special data for EAS or service signalingdata. The auxiliary streams or streams, if any, follow the DPs, which inturn are followed by dummy cells. When the PLS, EAC, FIC, DPs, auxiliarystreams and dummy data cells are mapped all together in the abovementioned order, i.e. the PLS, EAC, FIC, DPs, auxiliary streams anddummy data cells, cell capacity in the frame is exactly filled.

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) NFSS is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) have higher pilotdensity, allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the FSS(s) in a top-downmanner as shown in the figure. PLS1 cells are mapped first from a firstcell of a first FSS in increasing order of cell index. PLS2 cells followimmediately after a last cell of PLS1 and mapping continues downwarduntil a last cell index of the first FSS. If the total number ofrequired PLS cells exceeds the number of active carriers of one FSS,mapping proceeds to a next FSS and continues in exactly the same manneras the first FSS.

After PLS mapping is completed, DPs are carried next. If an EAC, an FICor both are present in a current frame, the EAC and the FIC are placedbetween the PLS and “normal” DPs.

Hereinafter, description will be given of encoding an FEC structureaccording to an embodiment of the present invention. As above mentioned,the data FEC encoder may perform FEC encoding on an input BBF togenerate an FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The illustrated FEC structure corresponds to theFECBLOCK. In addition, the FECBLOCK and the FEC structure have samevalue corresponding to a length of an LDPC codeword.

As described above, BCH encoding is applied to each BBF (Kbch bits), andthen LDPC encoding is applied to BCH-encoded BBF (Kldpc bits=Nbch bits).

A value of Nldpc is either 64,800 bits (long FECBLOCK) or 16,200 bits(short FECBLOCK).

Table 22 and Table 23 below show FEC encoding parameters for the longFECBLOCK and the short FECBLOCK, respectively.

TABLE 22 LDPC BCH error rate Nldpc Kldpc Kbch correction capabilityNbch-Kbch  5/15 64800 21600 21408 12 192  6/15 25920 25728  7/15 3024030048  8/15 34560 34368  9/15 38880 38688 10/15 43200 43008 11/15 4752047328 12/15 51840 51648 13/15 56160 55968

TABLE 23 LDPC BCH error rate Nldpc Kldpc Kbch correction capabilityNbch-Kbch  5/15 16200  5400  5232 12 168  6/15  6480  6312  7/15  7560 7392  8/15  8640  8472  9/15  9720  9552 10/15 10800 10632 11/15 1188011712 12/15 12960 12792 13/15 14040 13872

Detailed operations of BCH encoding and LDPC encoding are as below.

A 12-error correcting BCH code is used for outer encoding of the BBF. ABCH generator polynomial for the short FECBLOCK and the long FECBLOCKare obtained by multiplying all polynomials together.

LDPC code is used to encode an output of outer BCH encoding. To generatea completed Bldpc (FECBLOCK), Pldpc (parity bits) is encodedsystematically from each Ildpc (BCH—encoded BBF), and appended to Ildpc.The completed Bldpc (FECBLOCK) is expressed by the following Equation.

B _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁ ,p₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]  [Equation 2]

Parameters for the long FECBLOCK and the short FECBLOCK are given in theabove Tables 22 and 23, respectively.

A detailed procedure to calculate Nldpc−Kldpc parity bits for the longFECBLOCK, is as follows.

Initialize the parity bits

$\begin{matrix}{p_{0} = {p_{1} = {p_{2} = {\ldots = {p_{N_{ldpc} - K_{ldpc} - 1} = 0}}}}} & \lbrack {{Equation}\mspace{14mu} 3} \rbrack\end{matrix}$

2) Accumulate a first information bit—i0, at a parity bit addressspecified in a first row of addresses of a parity check matrix. Detailsof the addresses of the parity check matrix will be described later. Forexample, for the rate of 13/15,

p ₉₈₃ =p ₉₈₃ ⊕i ₀ p ₂₈₁₅ =p ₂₈₁₅ ⊕i ₀

p ₄₈₃₇ =p ₄₈₃₇ ⊕i ₀ p ₄₉₈₉ =p ₄₉₈₉ ⊕i ₀

p ₆₁₃₈ =p ₆₁₃₈ ⊕i ₀ p ₆₄₅₈ =p ₆₄₅₈ ⊕i ₀

p ₆₉₂₁ =p ₆₉₂₁ ⊕i ₀ p ₆₉₇₄ =p ₆₉₇₄ ⊕i ₀

p ₇₅₇₂ =p ₇₅₇₂ ⊕i ₀ p ₈₂₆₀ =p ₈₂₆₀ ⊕i ₀

p ₈₄₉₆ =p ₈₄₉₆ ⊕i ₀  [Equation 4]

3) For the next 359 information bits, is, s=1, 2, . . . , 359,accumulate is at parity bit addresses using following Equation.

{x+(s mod 360)×Q _(ldpc)}mod(N _(ldpc) −K _(ldpc))  [Equation 5]

Here, x denotes an address of a parity bit accumulator corresponding toa first bit i0, and Qldpc is a code rate dependent constant specified inthe addresses of the parity check matrix. Continuing with the example,Qldpc=24 for the rate of 13/15, so for an information bit i1, thefollowing operations are performed.

p ₁₀₀₇ =p ₁₀₀₇ ⊕i ₁ p ₂₈₃₉ =p ₂₈₃₉ ⊕i ₁

p ₄₈₆₁ =p ₄₈₆₁ ⊕i ₁ p ₅₀₁₃ =p ₅₀₁₃ ⊕i ₁

p ₆₁₆₂ =p ₆₁₆₂ ⊕i ₁ p ₆₄₈₂ =p ₆₄₈₂ ⊕i ₁

p ₆₉₄₅ =p ₆₉₄₅ ⊕i ₁ p ₆₉₉₈ =p ₆₉₉₈ ⊕i ₁

p ₇₅₉₆ =p ₇₅₉₆ ⊕i ₁ p ₈₂₈₄ =p ₈₂₈₄ ⊕i ₁

p ₈₅₂₀ =p ₈₅₂₀ ⊕i ₁  [Equation 6]

4) For a 361th information bit i360, an address of the parity bitaccumulator is given in a second row of the addresses of the paritycheck matrix. In a similar manner, addresses of the parity bitaccumulator for the following 359 information bits is, s=361, 362, . . ., 719 are obtained using Equation 6, where x denotes an address of theparity bit accumulator corresponding to the information bit i360, i.e.,an entry in the second row of the addresses of the parity check matrix.

5) In a similar manner, for every group of 360 new information bits, anew row from the addresses of the parity check matrix is used to findthe address of the parity bit accumulator.

After all of the information bits are exhausted, a final parity bit isobtained as below.

6) Sequentially perform the following operations starting with i=1.

p _(i) =p _(i) ⊕p _(i-1) , i=1,2, . . . ,N _(ldpc) −K_(ldpc)−1  [Equation 7]

Here, final content of pi (i=0, 1, . . . , Nldpc−Kldpc−1) is equal to aparity bit pi.

TABLE 24 Code rate Qldpc  5/15 120  6/15 108  7/15  96  8/15  84  9/15 72 10/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for the short FECBLOCK is in accordancewith t LDPC encoding procedure for the long FECBLOCK, except that Table24 is replaced with Table 25, and the addresses of the parity checkmatrix for the long FECBLOCK are replaced with the addresses of theparity check matrix for the short FECBLOCK

TABLE 25 Code rate Qldpc  5/15 30  6/15 27  7/15 24  8/15 21  9/15 1810/15 15 11/15 12 12/15  9 13/15  6

FIG. 29 illustrates time interleaving according to an embodiment of thepresent invention.

to (c) show examples of a TI mode.

A time interleaver operates at the DP level. Parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI.

DP_TI_TYPE (allowed values: 0 or 1): This parameter represents the TImode. The value of ‘0’ indicates a mode with multiple TI blocks (morethan one TI block) per TI group. In this case, one TI group is directlymapped to one frame (no inter-frame interleaving). The value of ‘1’indicates a mode with only one TI block per TI group. In this case, theTI block may be spread over more than one frame (inter-frameinterleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks NTI per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames PI spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): This parameter representsthe maximum number of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, and 8): This parameterrepresents the number of the frames IJUMP between two successive framescarrying the same DP of a given PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. This parameter is set to ‘0’ iftime interleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the delay compensation block for the dynamic configuration informationfrom the scheduler may still be required. In each DP, the XFECBLOCKsreceived from SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and contains adynamically variable number of XFECBLOCKs. The number of XFECBLOCKs inthe TI group of index n is denoted by NxBLOCK_Group(n) and is signaledas DP_NUM_BLOCK in the PLS2-DYN data. Note that NxBLOCK_Group(n) mayvary from a minimum value of 0 to a maximum value of NxBLOCK_Group_MAX(corresponding to DP_NUM_BLOCK_MAX), the largest value of which is 1023.

Each TI group is either mapped directly to one frame or spread over PIframes. Each TI group is also divided into more than one TI block (NTI),where each TI block corresponds to one usage of a time interleavermemory. The TI blocks within the TI group may contain slightly differentnumbers of XFECBLOCKs. If the TI group is divided into multiple TIblocks, the TI group is directly mapped to only one frame. There arethree options for time interleaving (except an extra option of skippingtime interleaving) as shown in the following Table 26.

TABLE 26 Modes Descriptions Option Each TI group contains one TI blockand is mapped directly 1 to one frame as shown in (a). This option issignaled in PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’ (NTI =1). Option Each TI group contains one TI block and is mapped to 2 morethan one frame. (b) shows an example, where one TI group is mapped totwo frames, i.e., DP_TI_LENGTH = ‘2’ (PI = 2) and DP_FRAME_INTERVAL(IJUMP = 2). This provides greater time diversity for low data-rateservices. This option is signaled in PLS2-STAT by DP_TI_TYPE = ‘1’.Option Each TI group is divided into multiple TI blocks and is 3 mappeddirectly to one frame as shown in (c). Each TI block may use a full TImemory so as to provide a maximum bit-rate for a DP. This option issignaled in PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = NTI, whilePI = 1.

Typically, the time interleaver may also function as a buffer for DPdata prior to a process of frame building. This is achieved by means oftwo memory banks for each DP. A first TI block is written to a firstbank. A second TI block is written to a second bank while the first bankis being read from and so on.

The TI is a twisted row-column block interleaver. For an sth TI block ofan nth TI group, the number of rows Nr of a TI memory is equal to thenumber of cells Ncells, i.e., Nr=Ncells while the number of columns Ncis equal to the number NxBLOCK_TI(n,s).

FIG. 30 illustrates a basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 30(a) shows a write operation in the time interleaver and FIG.30(b) shows a read operation in the time interleaver. A first XFECBLOCKis written column-wise into a first column of a TI memory, and a secondXFECBLOCK is written into a next column, and so on as shown in (a).Then, in an interleaving array, cells are read diagonal-wise. Duringdiagonal-wise reading from a first row (rightwards along a row beginningwith a left-most column) to a last row, Nr cells are read out as shownin (b). In detail, assuming z_(n,s,i) (i=0, . . . , N_(r)N_(c)) as a TImemory cell position to be read sequentially, a reading process in suchan interleaving array is performed by calculating a row index R_(n,s,i),a column index C_(n,s,i), and an associated twisting parameter T_(n,s,i)as in the following Equation.

$\begin{matrix}{{{{GENERATE}( {R_{n,s,i},C_{n,s,i}} )} = \mspace{11mu}\{ \mspace{304mu}{{R_{n,s,i} = {{mod}( {i,N_{r}} )}},\mspace{104mu}{T_{n,s,i} = {{mod}( {{S_{shift} \times R_{n,s,i}},N_{c}} )}},\mspace{11mu}{C_{n,s,i} = {{mod}( {{T_{n,s,i} + \lfloor \frac{i}{N_{r}} \rfloor},N_{c}} )}}} \}}\mspace{301mu}} & \lbrack {{Equation}\mspace{14mu} 8} \rbrack\end{matrix}$

Here, S_(shift) is a common shift value for a diagonal-wise readingprocess regardless of N_(xBLOCK_TI)(s) and the shift value is determinedby x_(BLOCK_TI_MAX) given in PLS2-STAT as in the following Equation.

$\begin{matrix}{{for}\mspace{14mu}\{ {\begin{matrix}{{N_{{{xBLOCK}\_{TI}}{\_{MAX}}}^{\prime} = {N_{{{xBLOCK}\_{TI}}{\_{MAX}}} + 1}},} & {{{if}\mspace{14mu} N_{{{xBLOCK}\_{TI}}{\_{MAX}}}\mspace{14mu}{mod}\; 2} = 0} \\{{N_{{{xBLOCK}\_{TI}}{\_{MAX}}}^{\prime} = N_{{{xBLOCK}\_{TI}}{\_{MAX}}}},} & {{{if}\mspace{14mu} N_{{{xBLOCK}\_{TI}}{\_{MAX}}}\mspace{14mu}{mod}\; 2} = 1}\end{matrix},{S_{shift} = \frac{N_{{{xBLOCK}\_{TI}}{\_{MAX}}}^{\prime} - 1}{2}}} } & \lbrack {{Equation}\mspace{14mu} 9} \rbrack\end{matrix}$

As a result, cell positions to be read are calculated by coordinatesz_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 31 illustrates an interleaving array in a TImemory for each TI group, including virtual XFECBLOCKs whenN_(xBLOCK_TI)(0,0)=3, N_(xBLOCK_TI)(1,0)=6, and N_(xBLOCK_TI)(2,0)=5.

A variable number N_(xBLOCK_TI)(n,s)=N_(r) may be less than or equal toN_(xBLOCK_TI_MAX)′. Thus, in order to achieve single-memorydeinterleaving at a receiver side regardless of N_(xBLOCK_TI)(n,s), theinterleaving array for use in the twisted row-column block interleaveris set to a size of N_(r)×N_(c)=N_(cells)×N_(xBLOCK_TI_MAX)′ byinserting the virtual XFECBLOCKs into the TI memory and a readingprocess is accomplished as in the following Equation.

  [Equation 10] p = 0; for i = 0; i < N_(cells)N_(xBLOCK)_TI_MAX^(′); i= i + 1 {GENERATE (R_(n,s,i), C_(n,s,i)); V_(i) = N_(r)C_(n,s,j) +R_(n,s,j)  if V_(i) > N_(cells)N_(xBLOCK)_TI(n,s)  {   Z_(n,s,p) =V_(i); p = p + 1;   } }

The number of TI groups is set to 3. An option of the time interleaveris signaled in the PLS2-STAT data by DP_TI_TYPE=‘0’,DP_FRAME_INTERVAL=‘1’, and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, andPI=1. The number of XFECBLOCKs, each of which has Ncells=30 cells, perTI group is signaled in the PLS2-DYN data by NxBLOCK_TI(0,0)=3,NxBLOCK_TI(1,0)=6, and NxBLOCK_TI(2,0)=5, respectively. A maximum numberof XFECBLOCKs is signaled in the PLS2-STAT data by NxBLOCK_Group_MAX,which leads to └N_(xBLOCK_Group_MAX)/N_(TI)┘=N_(xBLOCK_TI_MAX)=6.

The purpose of the Frequency Interleaver, which operates on datacorresponding to a single OFDM symbol, is to provide frequency diversityby randomly interleaving data cells received from the frame builder. Inorder to get maximum interleaving gain in a single frame, a differentinterleaving-sequence is used for every OFDM symbol pair comprised oftwo sequential OFDM symbols.

Therefore, the frequency interleaver according to the present embodimentmay include an interleaving address generator for generating aninterleaving address for applying corresponding data to a symbol pair.

FIG. 32 illustrates an interleaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode according to an embodiment of the presentinvention.

shows the block diagrams of the interleaving-address generator for 8KFFT mode, (b) shows the block diagrams of the interleaving-addressgenerator for 16K FFT mode and (c) shows the block diagrams of theinterleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described asfollows, exploiting a single interleaving-sequence. First, availabledata cells (the output cells from the Cell Mapper) to be interleaved inone OFDM symbol Om,l is defined as O_(m,l)=└x_(m,l,0), . . . ,x_(m,l,p), . . . , x_(m,l,N) _(data) ₋₁┘ for l=0, . . . , N_(sym)−1where xm,l,p is the pth cell of the lth OFDM symbol in the mth frame andNdata is the number of data cells: Ndata=CFSS for the frame signalingsymbol(s), Ndata=Cdata for the normal data, and Ndata=CFES for the frameedge symbol. In addition, the interleaved data cells are defined asP_(m,l)=└_(m,l,0), . . . , v_(m,l,N) _(data) ₋₁┘ for l=0, . . . ,N_(sym)−1.

For the OFDM symbol pair, the interleaved OFDM symbol pair is given byv_(m,l,h) _(l) _((p))=z_(m,l,p), p=0, . . . , N_(data)−1, for the firstOFDM symbol of each pair v_(m,l,p)=x_(m,l,H) _(l) _((p)), p=0, . . . ,N_(data)−1, for the second OFDM symbol of each pair, where H_(l)(p) isthe interleaving

address generated by a PRBS generator.

FIG. 33 illustrates a main PRBS used for all FFT modes according to anembodiment of the present invention.

illustrates the main PRBS, and (b) illustrates a parameter Nmax for eachFFT mode.

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleavingaddress for frequency interleaving according to an embodiment of thepresent invention.

illustrates a sub-PRBS generator, and (b) illustrates an interleavingaddress for frequency interleaving. A cyclic shift value according to anembodiment of the present invention may be referred to as a symboloffset.

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

FIG. 35 illustrates a write operation for two TI groups.

A left block in the figure illustrates a TI memory address array, andright blocks in the figure illustrate a write operation when two virtualFEC blocks and one virtual FEC block are inserted into heads of twocontiguous TI groups, respectively.

Hereinafter, description will be given of a configuration of a timeinterleaver and a time interleaving method using both a convolutionalinterleaver (CI) and a block interleaver (BI) or selectively usingeither the CI or the BI according to a physical layer pipe (PLP) mode. APLP according to an embodiment of the present invention is a physicalpath corresponding to the same concept as that of the above-describedDP, and a name of the PLP may be changed by a designer.

A PLP mode according to an embodiment of the present invention mayinclude a single PLP mode or a multi-PLP mode according to the number ofPLPs processed by a broadcast signal transmitter or a broadcast signaltransmission apparatus. The single PLP mode corresponds to a case inwhich one PLP is processed by the broadcast signal transmissionapparatus. The single PLP mode may be referred to as a single PLP.

The multi-PLP mode corresponds to a case in which one or more PLPs areprocessed by the broadcast signal transmission apparatus. The multi-PLPmode may be referred to as multiple PLPs.

In the present invention, time interleaving in which different timeinterleaving schemes are applied according to PLP modes may be referredto as hybrid time interleaving. Hybrid time interleaving according to anembodiment of the present invention is applied for each PLP (or at eachPLP level) in the multi-PLP mode.

FIG. 36 illustrates an interleaving type applied according to the numberof PLPs in a table.

In a time interleaving according to an embodiment of the presentinvention, an interleaving type may be determined based on a value ofPLP_NUM. PLP_NUM is a signaling field indicating a PLP mode. WhenPLP_NUM has a value of 1, the PLP mode corresponds to a single PLP. Thesingle PLP according to the present embodiment may be applied only to aCI.

When PLP_NUM has a value greater than 1, the PLP mode corresponds tomultiple PLPs. The multiple PLPs according to the present embodiment maybe applied to the CI and a BI. In this case, the CI may performinter-frame interleaving, and the BI may perform intra-frameinterleaving.

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver described above.

The hybrid time interleaver according to the first example may include aBI and a CI. The time interleaver of the present invention may bepositioned between a BICM chain block and a frame builder.

The BICM chain block illustrated in FIGS. 37 and 38 may include theblocks in the processing block 5000 of the BICM block illustrated inFIG. 19 except for the time interleaver 5050. The frame builderillustrated in FIGS. 37 and 38 may perform the same function as that ofthe frame building block 1020 of FIG. 18.

As described in the foregoing, it is possible to determine whether toapply the BI according to the first example of the structure of thehybrid time interleaver depending on values of PLP_NUM. That is, whenPLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI isapplied. When PLP_NUM>1, both the BI and the Cl may be applied (BI isturned ON). A structure and an operation of the Cl applied whenPLP_NUM>1 may be the same as or similar to a structure and an operationof the Cl applied when PLP_NUM=1.

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver described above.

An operation of each block included in the second example of thestructure of the hybrid time interleaver is the same as the abovedescription in FIG. 20. It is possible to determine whether to apply aBI according to the second example of the structure of the hybrid timeinterleaver depending on values of PLP_NUM. Each block of the hybridtime interleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver.

The hybrid time deinterleaver according to the first example may performan operation corresponding to a reverse operation of the hybrid timeinterleaver according to the first example described above. Therefore,the hybrid time deinterleaver according to the first example of FIG. 39may include a convolutional deinterleaver (CDI) and a blockdeinterleaver (BDI).

A structure and an operation of the CDI applied when PLP_NUM>1 may bethe same as or similar to a structure and an operation of the CDIapplied when PLP_NUM=1.

It is possible to determine whether to apply the BDI according to thefirst example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. That is, when PLP_NUM=1, the BDI is notapplied (BDI is turned OFF) and only the CDI is applied.

The CDI of the hybrid time deinterleaver may perform inter-framedeinterleaving, and the BDEI may perform intra-frame deinterleaving.Details of inter-frame deinterleaving and intra-frame deinterleaving arethe same as the above description.

A BICM decoding block illustrated in FIGS. 39 and 40 may perform areverse operation of the BICM chain block of FIGS. 37 and 38.

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver.

The hybrid time deinterleaver according to the second example mayperform an operation corresponding to a reverse operation of the hybridtime interleaver according to the second example described above. Anoperation of each block included in the second example of the structureof the hybrid time deinterleaver may be the same as the abovedescription in FIG. 39.

It is possible to determine whether to apply a BDI according to thesecond example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. Each block of the hybrid timedeinterleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CDI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

In what follows, a method for transmitting and receiving content dataand a signaling method in a broadcast system are described. Inparticular, described in more detail will be a signal processing methodapplied before physical layer signal processing.

In the present invention, FIT (Fast Information Table) may be called LLS(Link Layer Signaling) or LLS (Low Level Signaling). In the presentinvention, all of the fields/elements of each table may not be includedbut included selectively depending on the needs.

FIG. 41 is a receiver protocol stack according to an embodiment of thepresent invention.

A broadcast service may be delivered by using three functional layers.The three functional layers comprise a physical layer, a delivery layer,and a service management layer. The physical layer may provide amechanism by which signaling, service announcement, and IP streams aretransported to the broadcast/broadband physical layer. The deliverylayer may transport an object by using the ROUTE (Real-Time ObjectDelivery over Unidirectional Transport) protocol. The ROUTE protocolbased on UDP/IP multicast operation over the broadcast physical layerand the HTTP protocol based on the TCP/IP unicast operation over thebroadband physical layer may be used in the delivery layer. The servicemanagement layer supports a service of arbitrary type such as a linearTV or HTML4 application service to be delivered in the delivery layerand the physical layer.

Service signaling may provide service discovery and descriptioninformation and include two functional components-bootstrap signaling(FIT, LLS, and so on) and service layer signaling (SLS). These are theinformation required to discover and acquire a user service. By usingthe FIT, a receiver builds a basic service list and providesbootstrapping and discovery of SLS with respect to each broadcastservice. As an embodiment, an FIT may be delivered by using layer-2packets as link layer signaling. The FIT may be delivered from eachphysical layer frame and acquired immediately. SLS may provideinformation used or required for a receiver to discover or access abroadcast service and a content component of the broadcast service. Inan embodiment, if SLS is delivered over broadcast, it may be deliveredby using ROUTE/UDP/IP protocol from one of an LCT transport sessionincluding the ROUTE session and may be delivered with an appropriatecarousel rate supporting fast channel joining and switching. If SLS isdelivered over broadband, it may be delivered by using HTTP/TCP/IPprotocol.

FIG. 42 illustrates logical entities of service management, delivery,and physical layer and their relationship according to one embodiment ofthe present invention.

The ROUTE/LCT session and/or MMTP sessions delivering a contentcomponent of a broadcast service may be comprised as follows. A servicecontent component may be delivered by at least one ROUTE/LCT session orat least one MMTP session with respect to a broadcast delivery of alinear service which does not exhibit app-based enhancement. Forbroadcast delivery of a linear service showing app-based enhancement, aservice content component may be delivered by at least one ROUTE/LCTsession or zero or more MMTP sessions. For streaming of media componentsin the same service, MMTP and ROUTE sessions may be prohibited frombeing used together. In the case of broadcast delivery of an app-basedservice, service content components may be delivered by at least oneROUTE/LCT session.

Each ROUTE session includes at least one LCT session delivering acontent component which comprises a broadcast service. For delivery of astreaming service, an LCT session may deliver an individual component ofa user service such as a video or caption stream. A streaming media maybe formatted for each MPEG-DASH as DASG segments. Each MMTP session mayinclude at least one MMTP packet flow delivering a content component orMMT signaling. An MMTP packet flow employs MPUs to deliver a componentor MMT signaling message formatted per MMT. For delivery of an NRT userservice or system metadata, an LCT session may deliver a file-basedcontent item. A content file may include continuous (time-based) ordiscrete (non-time based) media component of an NRT service or includeservice signaling or metadata such as an ESG fragment.

A broadcast stream is extracted from an RF channel, which may be definedas a carrier frequency located in the center of specific bandwidth. PLPcorresponds to a portion of an RF channel. Each PLP has a specificmodulation and coding parameter. A PLP may be identified by a unique PLPidentifier (PLPID) within a broadcast stream to which the PLP belongs.

Each service may be identified by two types of forms for a serviceidentifier. One of them is a compact form used in an FIT, which isunique only within a broadcast area, and the other one is a globallyunique form, used in the SLS and ESG. A ROUTE session may be identifiedby a source IP address, destination IP address, and destination portnumber. An LCT session may be identified by a TSI (Transport SessionIdentifier) unique within a ROUTE session. Those properties common toLCT sessions and specific properties unique for each LCT session may beprovided by a ROUTE signaling structure which is called S-TSID(Service-based Transport Session Instance Description), and S-TSID formspart of service level signaling. Each LCT session may be delivered byone PLP. Different LCT sessions of a ROUTE session may be included inthe respective PLPs. Properties described for S-TSID may include a TSIvalue and PLPID of each LCT session, a descriptor about a deliveryobject/files, and application layer FEC parameters.

FIG. 43 illustrates a method for using service signaling forbootstrapping and service discovery according to an embodiment of thepresent invention.

In an embodiment of the present invention, signaling information may bedelivered directly in the form of a link layer packet or content of adedicated channel instead of being processed by IP packet encapsulation,which may be called LLS (Link Layer Signaling) or FIT (Fast InformationTable). The time a receiver starts operation upon receiving a broadcastsignal may become the LLS. LLS may be used for a receiver to build alist of services received by the receiver, such as a channel name and achannel number. Also, LLS may provide bootstrap information with which areceiver discovers SLS for each service. The bootstrap information mayinclude TSI of an LCT session, which delivers a destination IP address,destination port, and SLS.

SLS for each service may describe the properties of a service for makingmeaningful presentation of the service such as capability of a receiverrequired, location at which the service may be obtained, and a list ofcomponents. In the ROUTE/DASH system, SLS may include USBD (User ServiceBundle Description), S-TSID, and DASH MPD (Media PresentationDescription). A detailed description of the USBD will be given later.

Since separate service signaling is used for each service, a receiver isallowed to obtain only the SLS related to a desired service withoutparsing all of the SLS within a broadcast stream, thereby reducing anunnecessary processing load on the receiver. For optional broadbanddelivery of service signaling, an FIT may include an HTTP URL at which aservice signaling file may be obtained. If SLS signaling is updated,that event may be detected from the version field of the FIT. Andupdated signaling may be obtained from a broadcast or broadband signal.

As shown in FIG. 43, LLS may be used to obtain SLS, and SLS may be usedto obtain a service component delivered to a ROUTE/LCT transportsession. A receiver may obtain an FIT delivered to a physical layerframe of a specific frequency identified by a BSID (Broadcast StreamID). Each service identified by a service ID may provide SLSbootstrapping information. The SLS bootstrapping information may includePLPID, source IP address (sIP1), destination IP address (dIP1),destination port number (dPort1), and TSI (tsi-SLS). The receiver mayobtain SLS fragments delivered through an IP/UDP/LCT session and PLP.These fragments may be associated with one service. A USBD/USD fragmentmay include an URI which describes a service level attribute and refersto an S-TSID fragment and an URI which refers to an MPD fragment. AnS-TSID fragment may provide component acquisition information related toone service, DASH representation found in the MPD, and mapping to theTSI corresponding to a service component. The S-TSID may providecomponent acquisition information of a TSI form, DASH representationidentifier, and ID of a PLP delivering a DASH segment related to theDASH representation. By using the PLPID and TSI value, the receiver maycollect audio/video components and buffer DASH media segments byapplying appropriate decoding processing. The hierarchical signalingarchitecture of a broadcast system will be described in more detailbelow.

Service signaling provide bootstrap and discovery information about aservice which is currently “on the air”. ESG (Electronic Service Guide)provides user service declaration which declares contents accompanied bydetailed information including device capability, content rating, andpresentation schedule; available broadcast service; and a list ofcontents. The ESG information may be provided so that a user may selecta service or content by using the ESG information. The ESG informationmay be needed for a receiver to determine whether the user is allowed towatch content or use a service. Linkage between an ESG service and anSLS service may be described by a service identifier.

In general, link layer signaling may operate under the IP level. At thereceiver-side, link layer signaling may be obtained faster than IP levelsignaling. The link layer signaling may be obtained before sessionestablishment. Link layer signaling may be used for performing fastchannel scan and fast service acquisition in an efficient manner. Linklayer signaling may include binding information between servicesignaling and PLP.

SLS may include USBD and S-TSID metadata fragments. USBD may includeservice identification and device capability information. Also, USBD mayinclude other SLS fragments needed to access a service and a mediacomponent; and metadata needed for a receiver to determine a transportmode (broadcast and/or broadband). An S-TSID fragment may provide atransport session description about an MMTP session or ROUTE/LCT sessionto which a media content component is delivered and provide adescription about delivery objects delivered from the LCT session.

The streaming content signaling component of the SLS may correspond toMPD (Media Presentation Description). The MPD, a streaming content, maybe associated with linear services for delivery of DASH segments. TheMPD may be used for supporting app-based services and being associatedwith a DASH-formatted content component, may be used for controllingplay-out of the content. The MPD may provide a resource identifier foran individual media component of a linear/streaming service in the formof a segment URL and provide context of identified resources within themedia presentation. App-based enhancement signaling may be applied todelivery of an app-based enhancement component such as an applicationlogical file, NRT media file, on-demand content component, ornotification stream.

FIG. 44 illustrates an FIT according to an embodiment of the presentinvention

An FIT supports channel scan and service acquisition. An FIT enablespresentation of a service list meaningful for the user and includesinformation supporting service selection through channel up/downzapping. Also, an FIT includes information for locating the location ofbroadcast/broadband-based service layer signaling depending onavailability of signaling. The bitstream syntax of the FIT is shown inFIG. 44. In the following, description of each field is provided.

FIT_protocol_version: 8-bit unsigned integer indicating the version ofthe structure of FIT

broadcast_stream_id: 16-bit unsigned integer for identifying the overallbroadcast stream

FIT_section_number: this 4-bit field indicates a section number. An FITmay include a plurality of FIT sections.

Total_FIT_section_number: this 4-bit field indicates a total number ofFIT sections.

FIT_section_version: this 4-bit field indicates the version number ofthe FIT section and may be increased by one if information of the FITsection changes.

FIT_section_length: this 12-bit field may represent the number of bytesof the FIT section.

num_services: an 8-bit unsigned integer value, which may indicate thenumber of services described by an instance of the FIT. A service for atleast one component within each broadcast stream may be included.

service_id: a 16-bit unsigned integer value, which identifies thecorresponding service within the scope of the broadcast area.

SLS_data_version: an 8-bit unsigned integer number which is increasedwhen a change occurs in a service entry within the FIT or in a signalingtable for a service delivered through SLS. By monitoring the FIT only, areceiver may recognize the change of signaling with respect to aservice.

service_category: this 5-bit field indicates the service category.Examples of the service category are as shown below.

0x00: service category not indicated by the service_category

0x01: A/V service

0x02: audio service

0x03: app-based service

0x04-0x07: reserved for future use

0x08: ESG (Electronic Service Guide)

0x09-0x1F: reserved for future use

provider_id: an 8-bit field for identifying a provider which broadcastsa service

short_service_name_length: a 3-bit field, which indicates the number ofbyte pairs of the short_service_name field. If no short name is given toa service, this field may be set to 0.

short_service_name: indicates a short name of a service

service_status: indicates the status of a service (active/inactive,hidden/shown). The MSB may indicate the active/inactive status, and theLSB may indicate the hidden/shown status.

sp_indicator: needed for meaningful presentation, which indicateswhether at least one component has been protected.

num_service_level_descriptors: indicates the number of service leveldescriptors for the corresponding service.

service_level_descriptor( ): may include zero or more descriptors whichprovide additional information of a service

num_FIT_level_descriptors: indicates the number of FIT-level descriptorsfor the corresponding FIT.

FIT_level_descriptor( ): may include zero or more descriptors whichprovide additional information of the corresponding FIT.

FIG. 45 an FIT descriptor according to an embodiment of the presentinvention.

Zero or more descriptors providing additional information for a serviceor FIT may be included in the FIT. FIG. 45 shows locations of individualdescriptors or descriptor tags for descriptors being referenced.Descriptors do not necessarily be included in the table but may beincluded optionally or selectively. If a descriptor is used, thedescriptor may be located at a specified location (denoted by “M”) orlocated at other location (denoted by “O”). FIGS. 46 to 48 illustrateembodiments of individual descriptors shown in FIG. 45.

FIG. 46 illustrates an embodiment of broadcastsignaling_location_descriptor( ).

descriptor_tag: identifies the corresponding descriptor.

descriptor_length: identifies the length of the correspondingdescriptor.

IP_version_flag: 1-bit indicator which indicates whetherSLS_source_IP_address and SLS_source_IP_address use IPv4 address or IPv6address.

SLS_source_IP_address_flag: indicates whether a service signalingchannel source IP address for the corresponding service exists.

SLS_source_IP_address: includes a source IP address of a service layersignaling LCT channel of the corresponding service. It may use IPv4 orIPv6 address depending on the IP_version_flag field.

SLS_destination_IP_address: includes a destination IP address of theservice layer signaling LCT channel of the corresponding service. It mayuse IPv4 or IPv6 address depending on the IP_version flag field.

SLS_destination_UDP_port: indicates a destination UDP port number of theservice layer signaling LCT channel of the corresponding service.

SLS_TSI: indicates TSI of the service layer signaling LCT channel of thecorresponding service.

SLS_PLP_ID: may indicate the identifier of PLP which includes theservice layer signaling LCT channel of the corresponding service. ThisPLP may be more robust than the PLP of the service.

FIG. 47 illustrates an embodiment of inet_signaling_location_descriptor().

Inet_signaling_location_descriptor( ) include URL information with whicha receiver may obtain arbitrary type of data requested by an externalserver(s) through broadband. FIG. 47 illustrates the structure of thisdescriptor. If a single URL is used together with a query term whichobtains a signaling description via broadband, the descriptor may beincluded at the service level or FIT level.

descriptor_tag: a descriptor tag for identifying a descriptor

descriptor_length: indicates the length of a descriptor

provider_id: identifies a provider which broadcasts a service

URL_type: indicates the type of URL the identification types of whichaccording to the codes are given below.

URL_type—0x00: URL for a signaling server

URL_type—0x01: URL for an ESG server

URL_type—0x02-0xFF: reserved for future use

URL_bytes( ): represents a URL each character of which may be UTF-8encoded and used by a query term.

If resources are available in a broadband network environment,inet_signaling_location_descriptor( ) may provide the URL of theresources.

Suppose the resource type is SLS. If inet_signaling_location_descriptor() information is located at the FIT level, a receiver may retrieve theSLS for all of the services described in the FIT by using the URL of thedescriptor through broadband. If the resource is ESG,inet_signaling_location_descriptor( ) information may provide a singleURL at which the receiver may retrieve the ESG for all of the providersdescribed in the FIT through broadband.

If the resource type is SLS and inet_signaling_location_descriptor( )information is located at the service level descriptor, the receiver mayretrieve the SLS for the corresponding service by using the URL of thedescriptor through broadband. If the resource is ESG,inet_signaling_location_descriptor( ) information may provide a singleURL at which the receiver may retrieve the ESG for the correspondingservice through broadband.

FIG. 48 illustrates an embodiment of a query term wheninet_signaling_location_descriptor( ) is located at FIT level, and FIG.49 illustrates an embodiment of a query term wheninet_signaling_location_descriptor( ) is located at service level.

capabilities_descriptor( ) provides a list of capabilities required forprocessing of a service (for example, download protocol, FEC algorithm,wrapper/archive format, compression algorithm, and media type). Areceiver may avoid proposing a service with an unsupported performanceto the user by parsing and processing a performance descriptor.

FIG. 50 illustrates an XML format of the FIT shown and described inFIGS. 44 to 49. Descriptions about the elements given in the XML formatdo not overlap with the descriptions of the aforementioned fields.However, in the XML format, inclusion of the aforementioned descriptormay be indicated by the use field, and those elements specified as 0-nin the use field may not be included.

The embodiment of the structure of the field names and positionalrelationship thereof shown in FIG. 50 may be different from theembodiments of FIGS. 44 to 49, and the description of an actual fieldmay be applied to the same field.

FIG. 51 illustrates a service layer signaling data model according to anembodiment of the present invention.

SLS may provide detailed technical information with which a broadcastreceiver may discover and access a broadcast service and a contentcomponent of the broadcast service. SLS may include a set of XML-encodedmetadata fragments delivered to a dedicated LCT session. The LCT sessiondelivering SLS may be obtained from the bootstrap information includedin the FIT. SLS is defined at the service level and describes serviceproperties and access information. SLS may include a list of contentcomponents, information about how the list may be obtained, informationabout receiver performance required for generating meaningfulpresentation of a service, and so on. In the ROUTE/DASH system forlinear service delivery, SLS may include USBD, S-TSID, and DASH MPD. SLSfragments may be delivered through an LCT transport session with a knownTSI value.

FIG. 52 illustrates USBD according to one embodiment of the presentinvention.

USBD of FIG. 52 is another embodiment of the USBD of FIG. 5, anddescriptions common to both of the embodiments will not be repeated.USBD is the top-level or entry-point SLS fragment.

Descriptions of elements (attributes) included in the USBD of FIG. 52are as follows.

bundleDescription: root element of USBD

userServiceDescription: single instance of ATSC 3.0 service

@serviceId: globally unique identifier of ATSC 3.0 service

@atsc:serviceId: reference for the corresponding service entry withinLLT (FIT). The value of a service identifier assigned to the entry isthe same as the value of this attribute.

@atsc:fullMPDUri: reference to an MPU fragment including description fora content component of the ATSC 3.0 service delivered over broadcast oroptionally broadband.

@atsc:sTSIDUri: reference to an S-TSID fragment providing access to theparameters related to a transport session carrying the content of theATSC 3.0 service.

name: name of the ATSC 3.0 service assigned by the lang attribute

lang: language of the ATSC 3.0 service name. The language may bespecified according to the XML datatype (XML Schema Part 2 [7]).

serviceLanguage: available language of the ATSC 3.0 service. Thelanguage may be specified according to the XML datatype (XML Schema Part2 [7]).

atsc:capabilityCode: represents performance and a performance groupdefined in the ATSC 3.0 service announcement and personalizationstandard and represents performance of a receiver capable of generatingmeaningful expression of the corresponding ATSC service content. Theformat of this element may be the same as the atsc:capabilities elementdescribed based on the ATSC 3.0 service announcement and contentfragmentation of a personalized document.

deliveryMethod: container of transport related information pertaining tothe contents of the service over broadcast and (optionally) broadbandmodes of access

atsc:broadcastAppService: DASH representation delivered over broadcast,in multiplexed or non-multiplexed form, containing the correspondingmedia component(s) belonging to the ATSC 3.0 Service, across all Periodsof the affiliated Media Presentation.

basePattern: A character pattern for use by the ATSC receiver to matchagainst any portion of the Segment URL used by the DASH client torequest Media Segments of a parent Representation under its containingPeriod. A match implies that the corresponding requested Media Segmentis carried over broadcast transport.

FIG. 53 illustrates S-TSID according to one embodiment of the presentinvention.

S-TSID of FIG. 53 is another embodiment of the S-TSID of FIG. 6, anddescriptions common to both of the embodiments will not be repeated. TheS-TSID includes the overall transport session description about theROUTE session, LCT session, or MMTP session to which media contentcomponents delivering a service are delivered. The S-TSID may include adelivery object delivered in the LCT session or metadata about objectflow. The S-TSID may include additional information about a contentcomponent and payload format delivered through the LCT session. TheS-TSID is signaling data in service units.

Description of the element (attribute) included in the S-TSID of FIG. 53is given below.

@serviceId: reference to the corresponding service element within theLLS (FIT). The value of this attribute refers to the service within theFIT like the corresponding value of the service ID. This attribute maybe used when the ROUTE session and the MMTP session without the USD areused for broadcast delivery of the linear service.

RS: ROUTE session

@bsid: identifier of a broadcast stream within a content componentdelivering broadAppService. If this attribute is not present, thedefault broadcast stream includes PLP which carries an SLS fragment forthe ATSC 3.0 service. The ID value may be the same as the value of thebroadcast stream ID within the FIT.

@sIpAddr: source IP address (default: source address of a current ROUTEsession; M for the non-primary session)

@dIpAddr: destination IP address (default: destination address of acurrent ROUTE session; it is M for the non-primary session)

@dport: destination port (default: destination port of a current ROUTEsession; it is M for the non-primary session)

@PLPID: PIP ID for the ROUTE session (default: current PLP)

LS: LCT session

@tsi: TSI value

@PLPID: PLP ID (overrides default ROUTE session value)

@bw: maximum bandwidth

@startTime: start time

@endTime: end time

SrcFlow: source flow defined by the ATSC 3.0 delivery & synchronizationspec [3]

RprFlow: repair flow defined by the ATSC3.0 delivery & synchronizationspec [3]

MS: MMTP session

@versionNumber: the version number of the MMTP protocol used in thisMMTP session

@bsid: identifier of a broadcast stream delivering a content component.If this attribute is not present, the default broadcast stream includesPLP which carries an SLS fragment for the ATSC 3.0 service. The ID valuemay be the same as the value of the broadcast stream ID within the FIT.

@sIpAddr: source IP address

@dIpAddr: destination IP address

@dport: destination port

@packetId: ID (default: 0x00) of the MMTP packet carrying an MMTsignaling message of the MMTP session

@PLPID: PLP ID for the MMTP session (default: current PLP)

@bw: Maximum bandwidth

@startTime: start time of the MMTP session

@endTime: end time of the MMTP session

Each instance of the S-TSID may be referred to by the USBD fragment.

MPD is an SLS metadata fragment which corresponds to a linear service ofthe duration defined by a broadcaster and which includes a formalizeddescription of the DASH media presentation. Contents of the MPD providecontext for identified resources within the media presentation andresource identifiers for the segments. In the context of a broadcastservice, at least one representation conveyed by the MPD may betransmitted over broadcast.

If the MMTP session delivers a broadcast streaming service, the MMTsignaling message may be delivered by the MMTP. Each MMTP session mayinclude the MMT signaling message, its component, and a packetdelivering the MMT signaling message.

In an embodiment, the service signaling fragment is encapsulated by themetadata envelop defined in the 3GPP MBMS, allowing identification,versioning, and update of included fragments.

In what follows, signaling embodiments of the present invention will bedescribed.

FIG. 54 illustrates hierarchical signaling architecture according to anembodiment of the present invention.

In the embodiment of FIG. 54, two S-TSID instances may be delivered overthe ROUTE. The first S-TSID may provide access information about the LCTsessions belonging to the ROUTE session #1DP delivering contentcomponents of the service X. The second S-TSID may provide accessinformation about the LCT sessions belonging to the ROUTE session #Ndelivering content components of the service Y.

As shown in FIG. 54, the S-TSID includes signaling information about theLCT sessions in service units.

FIG. 55 illustrates a fast service scan signaling flow according to oneembodiment of the present invention.

A receiver may comprise a tuner, baseband processor, and internalstorage. The receiver may perform fast service scan by using the FIT.

The tuner of the receiver may tune to a specific frequency by using apredefined frequency list. And for each frequency, the tuner may waitfor signal acquisition.

If a signal is detected from the frequency list, the baseband processormay extract the FIT and deliver the extracted FIT to the middlewaremodule. The middleware module may deliver the FIT to the FIT parser.

The FIT parser may extract FIT information and parse data. Even if theFIG information is the same as the last scanned version number, it maybe preferable to parse the FIT information. And the receiver may storethe parsed information in the channel map.

FIG. 56 illustrates a full channel scan signaling flow according to anembodiment of the present invention.

If the receiver performs full-scan by using service signaling (USBD orUSD) with respect to an individual service, the receiver may store moreabundant information. For example, a longer service name may be obtainedfrom the USD, and a channel map may be stored by matching service IDvalues of the USD and FIT. The singling flow is described below.

The receiver may be tuned to a frequency by using a predefined frequencylist and wait for signal acquisition with respect to individualfrequency. If a signal is detected from the frequency list, the basebandprocessor may extract the FIT and deliver the extracted FIT to themiddleware module.

The receiver may check the FIT version information and parse the FITinformation according to the checking result. In an embodiment, if theversion is new, the middleware module may gather the FIT and deliver thegathered FIT to the FIT parser. The FIT parser may parse the data (FIT)and extract information. The extracted information may be stored in achannel map.

The receiver may obtain SLS boot strapping information from the FIT. Thereceiver may deliver the SLS bootstrapping information to the ROUTEclient. The receiver may extract the USD from the SLS and store theextracted USD by using a signaling filtering scheme. The USD may beparsed by the signaling parser. And the receiver may update the channelmap by mapping the service ID.

FIG. 57 illustrates a service acquisition method in the pure broadcastaccording to an embodiment of the present invention.

A video and audio segment may be delivered over pure broadcast by usingone ROUTE session; in this case, the service signaling structure will bedescribed below with reference to FIG. 57.

The USD, S-TSID, and MPD may be obtained and parsed. All of the tablesare needed for service acquisition.

A representation to be provided may be selected. In this case, theS-TSID may be checked to determine which representation to deliver overbroadcast.

The receiver may transmit the information obtained from signaling (UDS,S-TSID, and MPD) to the segment acquisition module. Therefore, thereceiver may provide a user preference. For example, the user preferencemay indicate that the user prefers Spanish audio language to Englishaudio language.

The segment acquisition module may determine by using the informationdescribed in the USD whether a component of a broadcast stream may beextracted. If the DASH client requests a segment from an internal proxyserver, the internal proxy server has to know whether to request thesegment from a remote broadband server or whether to wait to appear inthe broadcast stream. The USD may describe the unicast “base pattern”and multicast “base pattern” in a deliveryMethod element. The proxyserver may check whether the unicast base pattern or multicast basepattern is a sub-string of the URL presented by the DASH player andoperate according to the checking result.

In the case of pure broadcast, the receiver may not know the location atwhich a component may be obtained if the deliveryMethod element of theUSD is unavailable.

FIG. 58 illustrates a service acquisition method in the pure broadcastaccording to an embodiment of the present invention.

One service may be included in a plurality of ROUTE sessions. In thiscase, the S-TSID may allow access to all of the representationsincluding additional ROUTE session information. However, the additionalinformation may be optional for rendering a service.

FIG. 59 illustrates an ESG information acquisition method according toan embodiment of the present invention.

The ESG bootstrapping information via broadband may be signaled in theFIT. In an embodiment, all of ESG data may be delivered via broadband.Therefore, the ESG broadcast bootstrapping information may be replacedwith the ESG bootstrapping information. The URL type field of theaforementioned inet_signaling_location_descriptor( ) may indicate thetype of ESG or other information.

FIG. 60 illustrates a method for receiving a hybrid (multi-audiolanguage) service according to an embodiment of the present invention.

Two or more audio components corresponding to different languages may bedelivered via separate delivery paths (one is broadcast and the other isbroadband). In this case, the S-TSID may describe all of the broadcastcomponents so that the ROUTE client obtain a desired component. Also,the USD may include URL patterns for broadband and URL patterns forbroadcast. Therefore, if the DASH client issues a request for a segment,the receiver middleware may describe which segment is delivered viawhich path. Therefore, the middleware may know which segment is to berequested from a remote broadband server and which segment is to besearched for from broadcast.

FIG. 61 illustrates a method for receiving a broadcast signal employinghandoff according to an embodiment of the present invention.

The receiver may perform handoff reception from broadcast to broadbandor from broadband to broadcast by using the signaling described in theUSD. The USD describes which component is delivered via broadcast orbroadband. The receiver middleware may receive a component via broadcastor broadband if broadcast reception fails.

FIG. 62 illustrates a method for receiving a broadcast signal employingscalable coding according to an embodiment of the present invention.

The USD include performance information essential for rendering aservice. In an embodiment, as the performance information essential fordecoding video, video resolution information may be included in the USD.And the USD may have a value such as the ‘HD or UHD’. This indicatesthat the corresponding service may be provided as an HD or UHD service.

The receiver may identify the components required for rendering an UHDservice or HD service by using the MPD.

Method for Filtering Signaling Fragments

The LCT TOI (Transmission Object Identifier) field is split into threeparts so that the receiver may quickly filter target signalingfragments.

The first part is a fragment type part allocated for identifying thetype of a signaling fragment. The fragment type field may be allocatedto identify an individual type of the SLS fragment carried by an object.The type value of each fragment may represent ‘bundled’ for 0x00,USBD/USD for 0x01, S-TSID for 0x02, MPD for 0x03 and ‘reserved’ forthose value larger than 0x04, for example.

The second part is a fragment type extension part allocated foridentifying the sub-type of a fragment. One embodiment of allocating asub-type represents types of fragments included in an object in a bitmapformat so that individual fragments may be filtered out when multiplefragments are carried. Another embodiment indicates an instanceidentifier when multiple instances of a signaling fragment of the samefragment type are delivered.

The fragment type extension field may be a bitmap indicating whichfragments are included when an object includes multiple fragments. Whenan object includes one fragment, a value for identifying each sub-typeof a service signaling fragment based on a filtering request may beallocated. Values of fragment type extension fields according to anembodiment are shown in Table 27.

TABLE 27 Fragment Type Value Fragment Type Extension Value Description  0x00 Value 0b0000000000000001 USBD/ generated by USD is OR operationcontained in applied on this bundle the following 0b0000000000000010S-TSID is values contained in this bundle 0b0000000000000100 MPD iscontained in this bundle   0x01-0x03 16-bits hashed value derived Toenable from the url of Service Layer the client to Signaling fragmentfilter the fragment that has instance url in question before assemblingLCT packets ≥0x04 . . . Reserved

The third part is a version part. The version part identifies theversion of an object identified by the fragment type and fragment typeextension part. When an object contains one fragment, the version fieldcontains the version number of the fragment. When an object is a set offragments, this field may contain the version number of the object andidentify which fragment of the object has been changed.

Template-Based Compression

The XML signaling fragment may be compressed by not only a compressiontool such as Gzip but also an alternative means such as diff and patchtool. In the diff and patch process, the XML signaling template may beshared in advance between a transmitter and a receiver. A transmittermay compare two XML files-XML signaling template and XML signalinginstance—and generate and output the differences as Diff.

Diff is a generic XML signaling instance and may be encapsulated by theelement MetadataEnvelope. If Diff is generated at the transmitter-side,Diff may be encapsulated by the MetadataEnvelope element after beingencapsulated by the content of the update element. And theMetadataEnvelope may be transmitted to multiple receivers through asignaling channel. If a received metadatafragment element contains adiffupdate element, the receiver may recognize that the information hasbeen processed through the corresponding compression mode.

The receiver searches the cache which stores pre-shared signalingtemplates for the signaling template with the metadata URI attribute; ifthe signaling template is not found, the receiver may attempt to obtainthe signaling template by using the URL of the SignalingTemplateID.

The receiver may recover the signaling instance by applying thedelivered Diff to a retrieved signaling template. The instance of thesignaling fragment may have the pair of attribute metadataURI(SignalinginstanceID) and attribute version (SignalingInstanceVersion).Then only the difference from the part updated with respect to thetemplate has to be transmitted, and the complete file doesn't have to betransmitted. Therefore, in particular, if the difference from theoriginal complete fragment is small, the diff and patch operation may beoperated very efficiently compared with the conventional compressionscheme. In an embodiment, even when there is no update in theserver-side, a Diff message of “no Diff” may be delivered.

FIG. 63 is an XML instance notation illustrating a method forencapsulating Diff in a metadataEnvelope element.

FIG. 64 illustrates a method for template pre-sharing and diff-patchingaccording to an embodiment of the present invention.

Signaling of a template fragment may be identified by the URL includedin the content of the templateID element. The template itself may bepre-shared as it is patched through HTTP over broadband. When a receiverobtains a Diff message for the first time, the template may be cachedfor the use in a future. In an embodiment, the template may be receivedat particular time as a fragment instance, and a subsequent Diff messagemay be applied to instance generation.

As shown in FIG. 64, a signaling template may be pre-shared andidentified by signaling template ID information and/or signalingtemplate version information. A transmitter includes a Diff generatorwhich compares the template with a signaling instance and generates thedifference between them as Diff. A receiver includes a Diff applierwhich may apply the received Diff to the template and recover thesignaling instance. The transmitter-side may correspond to the consumerwhile the receiver-side may correspond to the signaling producer. Thesignaling instance may be identified by the signaling instance IDinformation and/or signaling instance version information.

FIG. 65 illustrates an FIT delivery method according to an embodiment ofthe present invention.

In the description above, described was an embodiment in which the FITis signaled in the link layer. However, as shown in FIG. 68, the FIT maybe delivered in a different method.

In the example of (1), the FIT may be delivered by being included in thePLP such as a service component. Alternatively, as shown in the exampleof (2), the FIT may be delivered through a dedicated logical channel ofthe physical layer. Or as shown in the example of (3), the FIT may bedelivered through a specific PLP, called a basic PLP, which deliverssignaling information.

SLS may be transmitted in the IP/UDP layer according to the MMTP orROUTE protocol.

FIG. 66 is a block diagram illustrating a hybrid broadcast receptionapparatus according to an embodiment of the present invention.

A hybrid broadcast system can transmit broadcast signals in connectionwith terrestrial broadcast networks and the Internet. The hybridbroadcast reception apparatus can receive broadcast signals throughterrestrial broadcast networks (broadcast networks) and the Internet(broadband). The hybrid broadcast reception apparatus may includephysical layer module(s), physical layer I/F module(s), service/contentacquisition controller, Internet access control module(s), a signalingdecoder, a service signaling manager, a service guide manager, anapplication signaling manager, an alert signal manager, an alertsignaling parser, a targeting signaling parser, a streaming mediaengine, a non-real time file processor, a component synchronizer, atargeting processor, an application processor, an A/V processor, adevice manager, a data sharing and communication unit, redistributionmodule(s), companion device(s) and/or an external management module.

The physical layer module(s) can receive a broadcast related signalthrough a terrestrial broadcast channel, process the received signal,convert the processed signal into an appropriate format and deliver thesignal to the physical layer I/F module(s).

The physical layer I/F module(s) can acquire an IP datagram frominformation obtained from the physical layer module. In addition, thephysical layer I/F module can convert the acquired IP datagram into aspecific frame (e.g., RS frame, GSE, etc.).

The service/content acquisition controller can perform control operationfor acquisition of services, content and signaling data related theretothrough broadcast channels and/or broadband channels.

The Internet access control module(s) can control receiver operationsfor acquiring service, content, etc. through broadband channels.

The signaling decoder can decode signaling information acquired throughbroadcast channels.

The service signaling manager can extract signaling information relatedto service scan and/or content from the IP datagram, parse the extractedsignaling information and manage the signaling information.

The service guide manager can extract announcement information from theIP datagram, manage a service guide (SG) database and provide a serviceguide.

The application signaling manager can extract signaling informationrelated to application acquisition from the IP datagram, parse thesignaling information and manage the signaling information.

The alert signaling parser can extract signaling information related toalerting from the IP datagram, parse the extracted signaling informationand manage the signaling information.

The targeting signaling parser can extract signaling information relatedto service/content personalization or targeting from the IP datagram,parse the extracted signaling information and manage the signalinginformation. In addition, the targeting signaling parser can deliver theparsed signaling information to the targeting processor.

The streaming media engine can extract audio/video data for A/Vstreaming from the IP datagram and decode the audio/video data.

The non-real time file processor can extract NRT data and file type datasuch as applications, decode and manage the extracted data.

The component synchronizer can synchronize content and services such asstreaming audio/video data and NRT data.

The targeting processor can process operations related toservice/content personalization on the basis of the targeting signalingdata received from the targeting signaling parser.

The application processor can process application related informationand downloaded application state and represent parameters.

The A/V processor can perform audio/video rendering related operationson the basis of decoded audio/video data and application data.

The device manager can perform connection and data exchange withexternal devices. In addition, the device manager can perform operationsof managing external devices connectable thereto, such asaddition/deletion/update of the external devices.

The data sharing and communication unit can process information relatedto data transmission and exchange between a hybrid broadcast receiverand external devices. Here, data that can be transmitted and exchangedbetween the hybrid broadcast receiver and external devices may besignaling data, A/V data and the like.

The redistribution module(s) can acquire information related to futurebroadcast services and content when the broadcast receiver cannotdirectly receive terrestrial broadcast signals. In addition, theredistribution module can support acquisition of future broadcastservices and content by future broadcast systems when the broadcastreceiver cannot directly receive terrestrial broadcast signals.

The companion device(s) can share audio, video or signaling data bybeing connected to the broadcast receiver according to the presentinvention. The companion device may be an external device connected tothe broadcast receiver.

The external management module can refer to a module for broadcastservices/content provision. For example, the external management modulecan be a future broadcast services/content server. The externalmanagement module may be an external device connected to the broadcastreceiver.

FIG. 67 is a block diagram illustrating a hybrid broadcast receiveraccording to an embodiment of the present invention.

The hybrid broadcast receiver can receive hybrid broadcast servicesthrough interworking of terrestrial broadcasting and a broadband networkin DTV services of a future broadcast system. The hybrid broadcastreceiver can receive broadcast audio/video (A/V) content transmittedthrough terrestrial broadcasting and receive enhancement data relatedthereto or part of broadcast A/V content through the broadband networkin real time. In the specification, the broadcast A/V content can bereferred to as media content.

The hybrid broadcast receiver may include a physical layer controllerD55010, a tuner D55020, a physical frame parser D55030, a link layerframe parser D55040, an IP/UDP datagram filter D55050, an ATSC 3.0digital TV (DTV) control engine D55060, an ALC/LCT+ client D55070, atiming controller D55080, a signaling parser D55090, a dynamic adaptivestreaming over HTTP (DASH) client D55100, an HTTP access client D55110,an ISO base media file format (BMFF) parser D55120 and/or a mediadecoder D55130.

The physical layer controller D55010 can control operations of the tunerD55020 and the physical frame parser D55030 using radio frequency (RF)information of a terrestrial broadcast channel that the hybrid broadcastreceiver intends to receive.

The tuner D55020 can receive a broadcast related signal through aterrestrial broadcast channel, process the received signal and convertthe signal into an appropriate format. For example, the tuner D55020 canconvert a received terrestrial broadcast signal into physical frames.

The physical frame parser D55030 can parse a received physical frame andacquire a link layer frame through processing related thereto.

The link layer parser D55040 can execute related operations foracquisition of link layer signaling or an IP/UDP datagram from the linklayer frame. The link layer parser D55040 can output at least one IP/UDPdatagram.

The IP/UDP datagram filter D55050 can filter a specific IP/UDP datagramfrom the received at least one IP/UDP datagram. That is, the IP/UDPdatagram filter D55050 can selectively filter an IP/UDP datagram, whichis selected by the ATSC 3.0 DTV control engine, from the at least oneIP/UDP datagram output from the link layer parser D55040. The IP/UDPdatagram filter D55050 can output an application layer transportprotocol packet such as ALC/LCT+.

The ATSC 3.0 DTV control engine D55060 can serve as an interface betweenmodules included in the hybrid broadcast receiver. In addition, the ATSC3.0 DTV control engine D55060 can deliver parameters necessary for eachmodule to each module and control operation of each module through theparameters. In the present invention, the ATSC 3.0 DTV control engineD55060 can transfer media presentation description (MPD) and/or an MPDURL to the DASH client D55100. In addition, the ATSC 3.0 DTV controlengine D55060 can transfer a delivery mode and/or a transport sessionidentifier (TSI) to the ALC/LCT+ client D55070. Here, the TSI indicatesan identifier of a session in which a transport packet including asignaling message such as MPD or MPD URL related signaling istransmitted, for example, ALC/LCT+ session corresponding to applicationlayer transport protocol or FLUTE session. In addition, the TSI cancorrespond to an asset ID of an MMT.

The ALC/LCT+ client D55070 can generate one or more ISO base media fileformat (ISO MMFF) objects by processing an application layer transportprotocol packet such as ALC/LCT+ and collecting and processing aplurality of packets. The application layer transport protocol packetmay include an ALC/LCT packet, an ALC/LCT+ packet, a ROUTE packet and/oran MMTP packet.

The timing controller D55080 can process a packet including system timeinformation and control a system clock according thereto.

The signaling parser D55090 can acquire and parse DTV broadcast servicerelated signaling, and generate and manage a channel map on the basis ofthe parsed signaling. In the present invention, the signaling parser canparse MPD or MPD related information extended from signalinginformation.

The DASH client D55100 can execute operations related to real-timestreaming or adaptive streaming. The DASH client D55100 can receive DASHcontent from an HTTP server through the HTTP access client D55110. TheDASH client D55100 can process a received DASH segment and output an ISOBMFF object. In the present invention, the DASH client D55100 candeliver a fully qualified representation ID or a segment URL to the ATSC3.0 DTV control engine D55060. Here, the fully qualified representationID can refer to an ID corresponding to a combination of an MPD URL,period@id and represenstation@id, for example. In addition, the DASHclient D55100 can receive the MPD or MPD URL from the ATSC 3.0 DTVcontrol engine D55060. The DASH client D55100 can receive a desiredmedia stream or DASH segment from the HTTP server using the received MPDor MPD URL. In the specification, the DASH client D55100 may be referredto as a processor.

The HTTP access client D55110 can request that the HTTP server providespecific information, receive a response to the request from the HTTPserver and process the response. Here, the HTTP server can process therequest received from the HTTP access client and provide a response tothe request.

The ISO BMFF parser D55120 can extract audio/video data from the ISOBMFF object.

The media decoder D55130 can decode the received audio/video data andperform processing for presentation of the decoded audio/video data.

To provide hybrid broadcast services through interworking of aterrestrial broadcast network and a broadband network according to thehybrid broadcast receiver of the present invention, MPD needs to beextended or modified. The aforementioned terrestrial broadcast systemcan transmit extended or modified MPD and the hybrid broadcast receivercan receive content through broadcasting or a broadband network usingthe extended or modified MPD. That is, the hybrid broadcast receiver canreceive the extended or modified MPD through terrestrial broadcastingand receive content through terrestrial broadcasting or a broadbandnetwork on the basis of the MPD. A description will be given of elementsor attributes that need to be additionally included in the extended ormodified MPD, compared to the conventional MPD. In the following, theextended or modified MPD is referred to as MPD.

The MPD can be extended or modified to represent ATSC 3.0 service. Theextended or modified MPD can additionally includeMPD@anchorPresentationTime, Common@presentable, Common.Targeting,Common.TargetDevice and/or Common@associatedTo.

MPD@anchorPresentationTime can indicate presentation time anchor ofsegments included in the MPD, that is, base time. In the following,MPD@anchorPresentationTime can be used as effective time of the MPD.MPD@anchorPresentationTime can indicate the earliest playback time fromamong segments included in the MPD.

The MPD may further include common attributes and elements. The commonattributes and elements can be applied to AdaptionSet and Representationin the MPD. Common@presentable can indicate that media described by theMPD is a presentable component.

Common.Targeting can indicate targeting properties and/orpersonalization properties of the media described by the MPD.

Common.TargetDevice can indicate a target device or target devices ofthe media described by the MPD.

Common@associatedTo can indicate adaptationSet and/or representationrelated to the media described by the MPD.

In addition, MPD@id, Period@id and AdaptationSet@id included in the MPDmay be necessary to specify media content described by the MPD. That is,the DASH client can specify content to be received on the basis of theMPD using MPD@id, Period@id and AdaptationSet@id and signal the contentto the ATSC 3.0 DTV control engine. The ATSC 3.0 DTV control engine canreceive the corresponding content and deliver the content to the DASHclient.

FIG. 68 illustrates a protocol stack of a future hybrid broadcast systemaccording to an embodiment of the present invention.

As shown in the figure, a future broadcast transmission systemsupporting IP based hybrid broadcasting can encapsulate audio or videodata of broadcast services in the ISO base media file format (BMFF).Here, a DASH segment or a media processing unit (MPU) of an MMT can beused for encapsulation. In addition, the future broadcast system canequally transmit the encapsulated data through a broadcast network andthe Internet or differently transmit the encapsulated data through thebroadcast network and the Internet according to attributes of therespective networks. Furthermore, the future broadcast system canequally transmit the encapsulated data using at least one of broadcastor broadband. In the case of a broadcast network using broadcast, thebroadcast system can transmit data encapsulated in the ISO BMFF throughan application layer transport protocol packet which supports real-timeobject transmission. For example, the broadcast system can encapsulatedata in a real-time object delivery over unidirectional transport(ROUTE) or MMTP transport packet. The broadcast system can process theencapsulated data into an IP/UDP datagram, load the IP/UDP datagram in abroadcast signal and transmit the broadcast signal. When broadband isused, the broadcast system can deliver the encapsulated data to areceiving side through streaming such as DASH.

In addition, the broadcast system can transmit broadcast servicesignaling information as follows. In the case of a broadcast networkusing broadcast, the broadcast system can transmit signaling informationthrough physical layers of the future broadcast transmission system andthe broadcast network according to signaling attributes. Here, thebroadcast system can transmit the signaling information through aspecific data pipe (DP) of a transport frame included in a broadcastsignal. Signaling information transmitted through broadcast may have aform of being encapsulated in a bitstream or IP/UDP datagram. Whenbroadband is used, the broadcast system can return and deliver signalingdata to a receiver in response to a request of the receiver.

In addition, the broadcast system can transmit broadcast service ESG orNRT content through the following method. In the case of a broadcastnetwork using broadcast, the broadcast system can encapsulate the ESG orNRT content in an application layer transport protocol packet, forexample, real-time object delivery over unidirectional transport (ROUTE)or MMTP transport packet. The broadcast system can generate an IP/UDPdatagram with the encapsulated ESG or NRT content, load the IP/UDPdatagram in a broadcast signal and transmit the broadcast signal. Whenbroadband is used, the broadcast system can return and deliver the ESGor NRT content to a receiver in response to a request of the receiver.

FIG. 69 illustrates a structure of a transport frame delivered to aphysical layer of the future broadcast transmission system according toan embodiment of the present invention.

The future broadcast system can transmit a transport frame usingbroadcast. In the figure, P1 located at the front of the transport framecan refer to a symbol including information for transport signaldetection. P1 can include tuning information and a receiver can decode apart L1 following P1 on the basis of a parameter included in the symbolP1. The broadcast system can include, in the part L1, information abouttransport frame configuration and characteristics of data pipes. Thatis, the receiver can obtain the information about the transport frameconfiguration and characteristics of data pipes by decoding the part L1.In addition, the receiver can acquire information that needs to beshared between DPs through a common DP. According to an embodiment, thetransport frame may not include the common DP.

Components such as audio, video and data in the transport frame areincluded in an interleaved DP region composed of DP1 to DPn andtransmitted. Here, DPs through which components constituting eachservice (channel) are transmitted can be signaled through L1 or a commonPLP.

In addition, the future broadcast system can transmit information forrapidly acquiring information about services included in a transportframe. That is, the future broadcast system enables a future broadcastreceiver to rapidly acquire broadcast services and content relatedinformation included in a transport frame. When services/contentgenerated by one or more broadcasting stations are present in thecorresponding frame, the future broadcast system can enable the receiverto efficiently recognize the services/content according to thebroadcasting stations. That is, the future broadcast system can include,in a transport stream, service list information about services includedin the transport stream, and transmit the transport stream including theservice list information.

When an additional channel, for example, a fast information channel(FIC) is present, the broadcast system can transmit broadcast servicerelated information through the additional channel such that thereceiver can rapidly scan broadcast services and content in acorresponding frequency. As shown in FIG. 44, the broadcast system caninclude, in the transport stream, information for broadcast service scanand acquisition and transmit the same. Here, the region including theinformation for broadcast service scan and acquisition may be referredto as an FIC. The receiver can acquire information about broadcastservices generated and transmitted by one or more broadcasting stationsand easily and rapidly scan broadcast services available therein usingthe information.

In addition, a specific DP included in the transport stream can serve asa base DP capable of rapidly and robustly delivering signaling aboutbroadcast services and content transmitted in the correspondingtransport frame. Data transmitted through each DP of the transport frameof the physical layer is as shown in the lower part of FIG. 44. That is,link layer signaling or an IP datagram can be encapsulated in a genericpacket in a specific format and then transmitted through a DP. Here, theIP datagram can include signaling data. Link (low) layer signaling caninclude signaling related to fast service scan/acquisition, contextinformation of IP header compression and emergency alert.

FIG. 70 illustrates a transport packet of an application layer transportprotocol according to an embodiment of the present invention.

An application layer transport session can be composed of a combinationof an IP address and a port number. When the application layer transportprotocol corresponds to ROUTE, a ROUTE session can be composed of one ormore layered coding transport (LCT) sessions. For example, when a singlemedia component (e.g., DASH representation) is delivered through asingle LCT transport session, one or more media components can bemultiplexed and delivered through a single application transportsession. Furthermore, one or more transport objects can be deliveredthrough a single LCT transport session, and each transport object can bea DASH segment associated with DASH representation delivered through thetransport session.

For example, when the application layer transport protocol is an LCTbased protocol, a transport packet can be configured as follows. Thetransport packet can include an LCT header, a ROUTE header and payloaddata. A plurality of fields included in the transport packet is asfollows.

The LCT header can include the following fields. A version field V canindicate version information of the corresponding transport protocolpacket. A field C can include a flag related to the length of acongestion control information field which will be described below. Afield PSI can indicate protocol-specific information, that is,information specific to the corresponding protocol. A field S canindicate a flag associated with the length of a transport sessionidentifier (TSI) field. A field O can indicate a flag associated withthe length of a transport object identifier (TOI) field. A field H canindicate whether a half-word (16 bits) is added to the lengths of theTSI field and the TOI field. A field A (close session flag) can indicatethat a session is closed or closure of the session is imminent. A fieldB (close object flag) can indicate that an object being transmitted isclosed or closure of the object is imminent. A code point field canindicate information related to encoding or decoding of a payload of thecorresponding packet. For example, payload type can correspond to theinformation. A congestion control information field can indicateinformation related to congestion control. For example, the informationrelated to congestion control can be a current time slot index (CTSI), achannel number or a packet sequence number in the corresponding channel.A transport session identifier field can indicate a transport fieldidentifier. A transport object identifier field can indicate anidentifier of an object transmitted through the corresponding transportsession.

A ROUTE (ALC) header can include additional information of the precedingLCT header, such as a payload identifier related to a forward errorcorrection scheme.

Payload data can indicate a data part of the payload of thecorresponding packet.

FIG. 71 illustrates a method for transmitting signaling data by thefuture broadcast system according to an embodiment of the presentinvention. Signaling data of the future broadcast system can betransmitted as shown in the figure. To enable the receiver to supportfast service/content scan and acquisition, the future broadcasttransmission system can transmit signaling data with respect to abroadcast service delivered through a corresponding physical layerframe, via a fast information channel (FIC). In the specification, theFIC can refer to information about a service list. Unless an additionalFIC is present, the signaling data may be delivered through a paththrough which link layer signaling is delivered. That is, signalinginformation including information about services and components (audioand video) thereof can be encapsulated in an IP/UDP datagram andtransmitted through one or more DPs in the physical layer frame.According to an embodiment, signaling information about services andservice components can be encapsulated in an application layer transportpacket (e.g. a ROUTE packet or an MMTP packet) and transmitted.

The upper part of FIG. 71 illustrates an example of delivering theaforementioned signaling data through an FIC or one or more DPs. Thatis, signaling data for supporting fast service scan/acquisition can bedelivered through the FIC and signaling data including detailedinformation about services can be encapsulated in an IP datagram andtransmitted through a specific DP. In the specification, the signalingdata including detailed information about services may be referred to asservice layer signaling.

The middle part of FIG. 71 illustrates an example of delivering theaforementioned signaling data through an FIC and one or more DPs. Thatis, signaling data for supporting fast service scan/acquisition can bedelivered through the FIC and signaling data including detailedinformation about services can be encapsulated in an IP datagram andtransmitted through a specific DP. In addition, part of signaling dataincluding information about a specific component included in a servicemay be delivered through one or more transport sessions in theapplication layer transport protocol. For example, part of the signalingdata can be delivered through one or more transport sessions in a ROUTEsession.

The lower part of FIG. 71 illustrates an example of delivering theaforementioned signaling data through an FIC and one or more DPs. Thatis, signaling data for supporting fast service scan/acquisition can bedelivered through the FIC and signaling data including detailedinformation about services can be delivered through one or more sessionsin a ROUTE session.

FIG. 72 illustrates a syntax of a fast information table (FIT) accordingto an embodiment of the present invention.

In the present invention, the FIT may be referred to as an FIC, SLT orlow level signaling (LLS). In addition, the FIT may be defined as asignaling structure included in LLS. In this case, some informationincluded in the FIT according to an embodiment of the present inventioncan be included in the LLS. The LLS corresponds to signaling informationdelivered through a payload of an IP packet having a well-knownaddress/port in a broadcast system.

The illustrated FIT may correspond to a signaling structure forsupporting broadcast service scan and acquisition in a receiver.Broadcast services and/or content generated by one or more broadcaststations may be delivered through a specific frequency. In this case,information necessary for this procedure may be signaled through the FITsuch that the receiver can rapidly and easily scan broadcasting stationscorresponding to the frequency and/or services and/or content of thebroadcast stations.

When a signaling structure proposed by the present invention is used,the receiver can scan services and a service acquisition speed of thereceiver can be reduced. While the syntax of the illustrated FIT isdescribed, information included in the FIT may be represented in otherformats such as XML.

According to the present invention, the FIT may be delivered through afast information channel (FIC) which is a separate channel in a physicallayer transport frame. Otherwise, the FIT may be delivered through acommon DP through which information that can be shared between datapipes of the physical layer can be delivered. Information included inthe FIT may be delivered through a link layer signaling delivery path orlink layer signaling, which is defined in the link layer. Otherwise, theFIT may be delivered through a service signaling channel through whichservice signaling is transmitted or a transport session of theapplication layer.

The FIT according to an embodiment of the present invention may includeFIT_protocol_version information, broadcast_stream_id information,FIT_data_version information, FIT_length information, num_providersinformation, esg_service_id information, signaling_on_inet_flaginformation, provider_id information, inet_server_URL_lengthinformation, inet_server URL[k] information, num_services information,service_id information, SLS_data_version information, service_categoryinformation, short_service_name_length information, short_service_nameinformation, sp_indicator information, service_status information,SLS_simpleservice information, capability_flag information,signaling_broadcast_flag information, capability_code information, asignaling_broadcast_info( ) element, num_service_level_descriptorinformation, a service_level_descriptor( ) element,num_FIT_level_descriptor information, an FIT_level_descriptor( ) elementand/or a CRC element.

The FIT_protocol_version information can indicate the protocol versionof the FIT. When the protocol related to the FIT is changed, theFIT_protocol_version information can indicates such protocol change.

The FIT_data_version information can indicate the data version of theFIT. When data in the FIT is changed, the FIT_data_version informationcan indicate such data change.

FIT_length information indicates the length (size) of informationsubordinate to the FIT. The FIT_length can indicate the length (or size)of the FIT.

The num_providers information indicates the number of broadcastersproviding the FIT or broadcasters providing services. The num_providersinformation may indicate the number of broadcasters providing an ESGservice.

The esg_service_id information is an identifier for identifying the ESGservice which provides an ESG. The esg_service_id information can beused separately from the aforementioned service_id information.

The signaling_on_inet_flag information indicates whether signalinginformation related to the ESG service is delivered through theInternet. The signaling_on_inet_flag information indicates whetherservice level signaling is delivered through a broadband network.

The provider_id information identifies a broadcaster which provides theESG service.

The inet_server_URL_length information can indicate the length of theURL of a server which provides signaling information related to the ESGservice.

The inet_server URL[k] information can indicate the URL of a serverwhich provides signaling information or service level signaling relatedto the ESG service.

The SLS_data_version information can indicate the data version ofservice level signaling.

The SLS_simpleservice information can indicate whether signaling whichreplaces SLS is transmitted in a layer in which the FIT is delivered.For example, in the case of a specific service, the receiver canconfigure signaling such that the corresponding service can be accessedusing only information included in the FIT before information of SLS isused. In this case, the SLS_simpleservice information can indicatewhether the corresponding service can be accessed using only informationincluded in the FIT. The SLS_simpleservice information can indicatewhether the corresponding service is a simple broadcast service. TheSLS_simpleservice information can indicate whether all componentsincluded in the corresponding service are delivered through a broadcastnetwork or some components are delivered through a broadband network.That is, the SLS_simpleservice information indicates whether thereceiver needs to access the broadband network in order to effectivelypresent one or more broadcast services.

The capability_flag information indicates whether capability relatedinformation is included in the FIT.

The signaling_broadcast_flag information can indicate whether servicelevel signaling is delivered through a broadband network.

The capability_code information indicates receiver capabilitiesnecessary to decode a component in a service to enable significantpresentation of the component.

The signaling_broadcast_info( ) element can include informationnecessary to acquire service level signaling when the service levelsignaling is delivered through a broadcast network. Thesignaling_broadcast_info( ) element can include information indicating alocation, address and/or region through which the service levelsignaling is delivered and/or information indicating a protocol used todeliver the service level signaling.

The num_FIT_level_descriptor information indicates the number ofdescriptors defined in the level (or layer) in which the FIT isdelivered.

The CRC( ) element can include information related to a CRC.

Information and/or elements which are not described in FIG. 162, fromamong information and/or elements included in the FIT, correspond toinformation/elements having the same names included in theaforementioned FIC, FIT, SLT and/or LLS and thus description thereof isomitted.

FIG. 73 illustrates description about information included in the FITaccording to an embodiment of the present invention.

The FIT may include FIT_protocol_version information,Broadcast_stream_id information, FIT_data_version information,FIT_length information, num_providers information, esg_service_idinformation, signaling_on_inet_flag information, provider_idinformation, inet_server_URL_length information, inet_server URL[k]information, num_services information, service_id information,SLS_data_version information, service_category information,short_service_name_length information, short_service_name information,sp_indicator information, service_status information, SLS_simpleserviceinformation, capability_flag information, signaling_broadcast_flaginformation, capability_code information, a signaling_broadcast_info( )element, num_service_level_descriptor information, aservice_level_descriptor( ) element, num_FIT_level_descriptorinformation, an FIT_level_descriptor( ) element and/or a CRC element.

The above information and/or elements correspond to the aforementionedinformation/elements and thus description thereof is omitted.

FIG. 74 illustrates a signaling connecting structure in a procedure inwhich the receiver acquires a service according to an embodiment of thepresent invention.

The receiver parses an FIT delivered through the physical layer (or thefirst layer). The receiver recognizes whether an FIT of a new version isdelivered by parsing the FIT_version information and parses the FIT whenthe new FIT is delivered.

In the present embodiment, when the FIT_version information has a valueof “002”, the receiver checks the signaling_broadcast_flag informationand/or information in the signaling_broadcast_info ( ) element andacquires service level signaling.

In the present embodiment, when the FIT_version information has a valueof “03”, the receiver can select a broadcaster which provides theservice using the provider_id information. The receiver can receiveservice level signaling related to the service provided by thecorresponding broadcaster through a broadband network (Internet) usingthe signaling_over_inet_flag information and/or information in thesignaling_over_inet_information ( ) element. The receiver may check thesignaling_broadcast_flag information and/or information in thesignaling_broadcast_info ( ) element and acquire service levelsignaling.

In the present embodiment, SLS with respect to service 1 (Srv1) isdelivered through a broadcast network, whereas SLS with respect toservice 2 (Srv2) is delivered through a broadband network. Since LLSincluding the FIT can be delivered through a predetermined region orlocation in a broadcast signal, as described above, the receiver canacquire the LLS and/or the FIT from the corresponding region orlocation.

FIG. 75 illustrates a syntax of an FIT according to another embodimentof the present invention.

The FIT according to another embodiment of the present invention mayinclude FIT_protocol_version information, broadcast_stream_idinformation, FIT_data_version information, FIT_length information,num_providers information, num_services information, service_idinformation, SLS_data_version information, service_category information,short_service_name_length information, short_service_name information,sp_indicator information, service_status information, SLS_simpleserviceinformation, num_service_level_descriptor information, aservice_level_descriptor( ) element, num_provider_level_descriptorinformation, a provider_level_descriptor( ) element,num_FIT_level_descriptor information, an FIT_level_descriptor( )information and/or a CRC element.

The FIT according to another embodiment of the present inventionincludes the num_provider_level_descriptor information and theprovider_level_descriptor( ) element in addition to the aforementionedFIT and presents loops for performing signaling per provider(broadcaster) and per service.

The num_provider_level_descriptor information indicates the number ofdescriptors which provide information related to a broadcaster.

The provider_level_descriptor( ) element can include a descriptorproviding information related to the broadcaster.

According to the present embodiment, even when a plurality ofbroadcasters is present, it is possible to signal information foracquiring services provided by the respective broadcasters using thesignaling structure of the same FIT.

Information and/or elements which are not described in FIG. 162, fromamong information and/or elements included in the FIT, correspond toinformation/elements having the same names included in theaforementioned FIC, FIT, SLT and/or LLS and thus description thereof isomitted.

FIG. 76 is a table showing descriptor type and locations at whichdescriptors can be included according to an embodiment of the presentinvention.

The aforementioned signaling structure may include acapability_descriptor, a signaling_broadcast_descriptor and/or asignaling_over_internet_descriptor.

The capability_descriptor can include signaling information whichspecifies capabilities required for the receiver to effectively presenta service, content and/or a component. The capability_descriptor is aservice level descriptor and can be included in an FIT or an SLT.

The signaling_broadcast_descriptor can include information necessary tobootstrap (acquire) service level signaling included in a broadcastsignal and delivered. The signaling_broadcast_descriptor can includeinformation indicating source IP addresses, destination IP addressesand/or destination ports of packets which deliver the service levelsignaling. The signaling_broadcast_descriptor can include SLS_PLP_IDcorresponding to information identifying a PLP through which the servicelevel signaling is delivered and/or SLS_TSI information identifying aTSI of a transport session through which the service level signaling isdelivered. The SLS_PLP_ID information can be included in a signalingstructure delivered in the link layer as necessary.

The signaling_over_internet_descriptor can include informationindicating whether the service level signaling can be delivered throughthe Internet and/or address information of a server which provides theservice level signaling.

FIG. 77 illustrates a signaling_broadcast_descriptor according to anembodiment of the present invention.

The signaling_broadcast_descriptor according to the present embodimentmay include descriptor_tag information, descriptor_length information,IP_version_flag information, SLS_src_IP_addr flag information,SLS_src_P_addr information, SLS_dst_IP_addr information,SLS_dst_port_num information, SLS_TSI information and/or SLS_PLP_idinformation.

The descriptor_tag information specifies the corresponding descriptor.

The descriptor_length information indicates the length of thedescriptor.

The IP_version_flag information indicates the IP version used for an IPaddress delivered in the descriptor.

The SLS_src_IP_addr flag information indicates whether theSLS_src_IP_addr information is present.

The SLS_src_IP_addr information indicates source IP addresses of packetswhich deliver SLS.

The SLS_dst_IP_addr information indicates destination IP addresses ofpackets which deliver SLS.

The SLS_dst_port_num information indicates destination port numbers ofpackets which deliver SLS.

The SLS_TSI information identifies a transport session through which SLSis delivered.

The SLS_PLP_id information identifies a location/region in which SLS isdelivered. The SLS_PLP_id information indicates a PLP including the SLS.The SLS_PLP_id information may be included in link layer signaling anddelivered.

FIG. 78 illustrates meaning of the signaling_on_inet_descriptor (orsignaling_over_internet_descriptor) and values of theinet_server_URL_type information according to an embodiment of thepresent invention.

The signaling_on_inet_descriptor may include descriptor_tag information,descriptor_length information, num_inet_URL information, inet_serverURL_type information, inet_server_URL_length information and/orinet_server_URL information.

The descriptor_tag information identifies the corresponding descriptor.

The descriptor_length information indicates the length of thedescriptor.

The num_inet_URL information indicates the number of Internet URLaddresses signaled in the descriptor.

The inet_server_URL_type information indicates the type of data providedby a server corresponding to a signaled Internet URL. The type of dataprovided by the corresponding server can be identified according to avalue allocated to the inet_server_URL_type information. Referring tothe figure, when the inet_server URL type information has a value of“0x01”, the inet_server URL_type information can indicate a server whichdelivers SLS. When the inet_server URL_type information has a value of“0x02”, the inet_server_URL_type information can indicate a server whichprovides an ESG (Electronic Service Guide). When the inet_serverURL_type information has a value of “0x03”, the inet_server URL typeinformation can indicate a server which provides a template. When theinet_server URL_type information has a value of “0x04”, the inet_serverURL_type information can indicate a server which provides all types ofdata. URL type which can be provided by one provider can be diversifiedby defining type of each URL as described above. In addition, the FITsize can be reduced by using one URL for the provider level inconsideration of shortcomings of URL that the length is not restricted.

The inet_server_URL_length information indicates the URL length of aserver.

The inet_server URL information indicates the URL of a server.

FIG. 79 illustrates meaning of the capability_descriptor and values ofthe capability_category information according to an embodiment of thepresent invention.

The capability_descriptor according to the present embodiment mayinclude descriptor_tag information, descriptor_length information,num_capability information, capability_category information,capability_code_type information, capability_code_int information,capability_code_string_length information and/or capability_code_stringinformation.

The descriptor_tag information identifies the corresponding descriptor.

The descriptor_length information indicates the length of thedescriptor.

The num_capability information indicates the number of signaledcapabilities.

The capability_category information identifies capability category. Inone embodiment, the capability_category information can indicate thatcapabilities for download protocols are signaled when thecapability_category information is “0x01”, indicate that capabilitiesfor an FEC algorithm are signaled when the capability_categoryinformation is “0x02”, indicate that capabilities for wrapper/archiveformats are signaled when the capability_category information is “0x03”,indicate that capabilities for compression algorithms are signaled whenthe capability_category information is “0x04”, indicate thatcapabilities for media types are signaled when the capability_categoryinformation is “0x05” and indicate that capabilities for deliveryprotocols are signaled when the capability category information is“0x06”.

The capability_code_type information indicates capability_code type.

The capability_code_int information indicates a capability code. Thecapability code can correspond to information indicating a degree ofreceiver capability.

The capability_code_string_length information indicates a string lengthof the capability code.

The capability_code_string information indicates a capability code.

The capability code can be defined in the form of an integer or a stringaccording to the capability_code_int information or thecapability_code_string information.

FIG. 80 illustrates a syntax of an FIT according to another embodimentof the present invention.

The FIT according to another embodiment of the present invention mayinclude FIT_protocol_version information, broadcast_stream_idinformation, FIT_data_version information, FIT_length information,num_providers information, num_services information, service_idinformation, SLS_data_version information, service_category information,short_service_name_length information, short_service_name information,sp_indicator information, service_status information, SLS_simpleserviceinformation, signaling_broadcast_flag information, IP_version_flaginformation, SLS_src_IP_addr_flag information, SLS_src_IP_addrinformation, SLS_dst_IP_addr information, SLS_dst_port_num information,SLS_TSI information, SLS_PLP_id information,num_service_level_descriptor information, a service_level_descriptor( )element, num_provider_level_descriptor information, aprovider_level_descriptor( ) element, num_FIT_level_descriptorinformation, an FIT_level_descriptor( ) element and/or a CRC element.

The IP_version_flag information, SLS_src_IP_addr flag information,SLS_src_IP_addr information, SLS_dst_IP_addr information,SLS_dst_port_num information, SLS_TSI information and/or SLS_PLP_idinformation can be defined as a signaling_broadcast_info( ) element.

The IP_version_flag information indicates the IP version used for the IPaddress delivered in the corresponding descriptor.

The SLS_src_IP_addr flag information indicates whether theSLS_src_IP_addr information is present.

The SLS_src_IP_addr information indicates source IP address of packetswhich deliver SLS.

The SLS_dst_IP_addr information indicates destination IP address ofpackets which deliver SLS.

The SLS_dst_port_num information indicates destination port numbers ofpackets which deliver SLS.

The SLS_TSI information indicates a transport session through which SLSis delivered.

The SLS_PLP_id information identifies a location/region at which SLS isdelivered. The SLS_PLP_id information identifies a PLP including theSLS. The SLS_PLP_id information may be included in link layer signalingand delivered.

Information or elements included in the FIT according to anotherembodiment of the present invention correspond to the aforementionedinformation or elements having the same names and thus descriptionthereof is omitted.

According to the present embodiment, bootstrapping information about SLScan be signaled using a flag instead of a descriptor. In this case, theFIT size can be reduced.

FIG. 81 compares methods for signaling information about service levelsignaling delivered through a broadcast network according to anembodiment of the present invention.

The information included in the aforementionedsignaling_broadcast_descriptor may be signaled through the FIT by beingincluded in the aforementioned signaling_broadcast_info( ) element.

In this case, the descriptor_tag information and/or thedescriptor_length information included in thesignaling_broadcast_descriptor may be omitted, and thus up to 2 bytesfrom among bytes allocated for FIT signaling can be reduced.

FIG. 82 is a table showing descriptor type and locations at whichdescriptors can be included according to an embodiment of the presentinvention.

According to the present embodiment, a capability_descriptor can beincluded in a service level descriptor and asignaling_over_internet_descriptor can be included in a provider leveldescriptor.

Information that can be included in each descriptor has been described.

According to the present embodiment, the FIT may not separately includethe signaling_broadcast_descriptor, and the signaling_broadcast_info( )element can signal information necessary to bootstrap service levelsignaling.

FIG. 83 illustrates an FIT in XML format according to another embodimentof the present invention.

The FIT according to the present embodiment may include@protocol_version information, @Broadcast_stream_id information,@FIT_data_version information, a provider element, an inet_server_URLelement, @type information, a service element, @service_id information,@SLS_data_version information, @service_category information,@service_name information, @sp_indicator information, @service_statusinformation, @SLS_simpleservice information, a capability element, asignaling_broadcast element, a service_level_descriptor element, asignaling_on_inet_URL element, a provider_level_descriptor( ) element,an FIT_level_descriptor( ) element and/or a CRC( ) element.

The provider element includes information about a provider. The providerelement can signal information about 0 to N providers.

The inet_server_URL element includes information indicating the URL of aserver which provides data through the Internet.

The @type information indicates the type of data provided by the serverhaving the URL identified by the inet_server_URL element. The @typeinformation can identify a server delivering SLS, a server providing anESG, a server providing a template and a server providing all types ofdata according to values thereof.

The capability element can include information contained in theaforementioned capability_descriptor.

The signaling_broadcast element can include information contained in theaforementioned signaling_broadcast_descriptor.

FIG. 84 illustrates description about information included in an FITaccording to an embodiment of the present invention.

The FIT may include FIT_protocol_version information,broadcast_stream_id information, FIT_data_version information,FIT_length information, num_providers information, num_servicesinformation, service_id information, SLS data version information,service_category information, short_service_name_length information,short_service_name information, sp_indicator information, service_statusinformation, SLS_simpleservice information, capability_flag information,signaling_broadcast_flag information, capability_code information,num_service_level_descriptor information, a service_level_descriptor( )element, num_provider_level_descriptor information, aprovider_level_descriptor( ) element, num_FIT_level_descriptorinformation, an FIT_level_descriptor( ) element and/or a CRC element.

The SLS_simpleservice information can indicate whether a service is asimple broadcast service. The SLS_simpleservice information can indicatewhether all components included in the service are delivered through abroadcast network or some components are delivered through a broadbandnetwork. That is, the SLS_simpleservice information indicates whetherthe receiver needs to access the broadband network in order toeffectively present one or more broadcast services.

The num_provider_level_descriptor information indicates the number ofprovider level descriptors.

The provider_level_descriptor( ) element can include a provider leveldescriptor including description information about a provider.

The aforementioned information and/or elements have been describedabove.

FIG. 85 illustrates a signaling connecting structure in a procedure inwhich the receiver acquires a service according to an embodiment of thepresent invention.

In the present embodiment, service 1 (Srv1) and service 2 (Srv2) aredelivered through a broadcast stream. SLS for each service is deliveredthrough a broadcast network.

In this case, the receiver accesses a dedicated region in which an FITis delivered in a broadcast signal to acquire the FIT and obtains theFIT_version information of the FIT. When the version of the FIT has beenchanged, the receiver parses the FIT.

The receiver acquires information about service 1 and service 2 in loopsfor service 1 and service 2 in the FIT. The information about theservices is shown in the figure. Particularly, the information caninclude a signaling_broadcast_descriptor ( ) element. Thesignaling_broadcast_descriptor ( ) element can include theaforementioned signaling_broadcast_descriptor and the receiver canacquire SLS for service 1 and SLS for service 2 using informationincluded in the signaling_broadcast_descriptor.

The receiver can acquire the SLS for each service and access a sessiondelivering components included in service 1 and/or service 2 using theSLS information. The receiver acquires components for presenting theservices from the corresponding session and present service 1 and/orservice 2 viewers.

FIG. 86 illustrates a signaling connecting structure in a procedure inwhich the receiver acquires a service according to another embodiment ofthe present invention.

In the present embodiment, service 1 (Srv1) and service 2 (Srv2) aredelivered through a broadcast stream. SLS for service 1 can be deliveredthrough a broadcast network, whereas SLS for service 2 can be deliveredthrough a broadband network.

In this case, the receiver acquires an FIT by accessing a dedicatedregion in which the FIT is delivered in a broadcast signal and obtainsthe FIT_version information of the FIT. When the version of the FIT hasbeen changed, the receiver parses the FIT.

The receiver acquires information about service 1 and service 2 in loopsfor service 1 and service 2 in the FIT. The information about theservices is shown in the figure. Particularly, the loop for service 1can include a signaling_broadcast_descriptor ( ) element and the loopfor service 2 can include a signaling_on_inet_URL_descriptor ( )element.

The signaling_broadcast_descriptor ( ) element can include theaforementioned signaling_broadcast_descriptor and the receiver canacquire SLS for service 1 using information in the signalingbroadcast_descriptor.

The signaling_on_inet_URL_descriptor ( ) element can include theaforementioned signaling_on_inet_descriptor and the receiver can acquireSLS delivered through the broadband network using information in thesignaling_on_inet_descriptor.

The receiver can access a session delivering components included inservice 1 and/or service 2 using the acquired SLS information. Thereceiver acquires the components for presenting the services from thecorresponding session and presents service 1 and/or service 2 toviewers.

FIG. 87 illustrates a template delivery table according to an embodimentof the present invention.

As described above, signaling information such as SLS may be transmittedby using a template-based compression method. In other words, signalinginformation may be managed through Diff and patch process. A signalingtemplate may be pre-shared between a transmitter and a receiver.

A template may be transmitted in the format of a signaling table asshown in FIG. 87. The fields included in the template delivery table ofFIG. 87 are described below.

Table_ID: indicates an identifier of a template delivery table

Version_Number: indicates the version of the template delivery table

Table_length: indicates the length of the template delivery table

encoding_type: indicates the encoding type of the template deliverytable

Table_id_extension: extends the table identifier of the templatedelivery table

current_segment_number: indicates the current segment number of adescriptor for the template delivery table

last_segment_number: indicates the last segment number of a descriptorfor the template delivery table

Signaling_id: indicates the signaling ID of the template delivery table

Signaling_version: indicates the signaling version of the templatedelivery table

Template_id: indicates the ID of a template included in the templatedelivery table

Template_version: indicates the version of a template included in thetemplate delivery table

template_length: indicates the length of a template included in thetemplate delivery table

template: template information included in the template delivery table

As described in detail above, service signaling information may bestored as a (signaling) template. And if a signaling instance whichchanges the service signaling information is generated, a transmittermay transmit the difference between the template and the signalinginstance by generating Diff. A receive may recover the signalinginstance by applying the Diff to a pre-shared template and apply therecovered signaling instance to a system/data. Such a signaling templatemay be pre-shared with the receiver in the form of template deliverytable.

FIG. 88 illustrates a level descriptor according to an embodiment of thepresent invention.

In an embodiment of the present invention, a descriptor may be includedin a table depending on the needs. Also, a descriptor may be includedfor each level. In FIG. 88, capability_descriptor,signaling_broacdast_descriptor, and signaling_on_internet_discriptor maybe referred to as capability information, broadcast signalinginformation, and URL signaling information, respectively. Descriptionabout each information of FIG. 88 is substituted for by the detaileddescription given above.

An FIT may include signaling information at the FIT level and signalinginformation at the service level. The signaling information at the FITlevel is the information applied to the entire services described by theFIT, and the signaling information at the service level is theinformation applied to an individual service described by the FIT. It isa waste of resources to always include the signaling information appliedto the entire services for each individual service. Therefore, thesignaling information applied to the entire services is included at theFIT level. It is preferable that the signaling information for eachindividual service should be included at the service level.

In the embodiment of FIG. 88, capability_descriptor, signaling_broacdastdescriptor, and signaling_on_internet_discriptor may all be signaled atthe service level. However, signaling_on_internet_discriptor may also besignaled at the FIT level. signaling_on_internet_descriptor may includea URL at which an ESG or other signaling file may be obtained.

If URL signaling information is included at the FIT level, thecorresponding URL may represent a URL at which signaling informationabout all of the broadcast services described in the FIT may beretrieved over broadband. If URL signaling information is included atthe FIT level, the corresponding URL may represent a URL at which all ofthe providers described in the FIT or an ESG about the correspondingservices may be retrieved over broadband.

If URL signaling information is included at the service level, thecorresponding URL may represent a URL at which signaling informationabout a service including URL signaling information may be retrievedover broadband. If URL signaling information is included in the FITlevel, the corresponding URL may represent a URL at which an ESGincluding the URL signaling information may be retrieved over broadband.The URL signaling information may be included at both of the service andFIT levels.

FIG. 89 illustrates an FIT to which level descriptors are appliedaccording to an embodiment of the present invention.

In FIG. 89, descriptions about the information included in the FIT arereplaced with the detailed descriptions given above.

In the FIT of FIG. 89, as described with reference to FIG. 88,signaling_broacdast_descriptor information,signaling_on_internet_descriptor information, and capability_descriptormay be included in the FIT as service level descriptors. A service leveldescriptor may be included selectively/optionally depending on theneeds. And signaling_on_internet_descriptor information may be includedin the FIT as an FIT level descriptor. The FIT level descriptor may alsobe selectively/optionally included depending on the needs.

The signaling structure as shown in FIG. 89 may improve flexibility ofsignaling table/resource utilization. In other words, sincesignaling_broacdast_descriptor information,signaling_on_internet_discriptor information, and capability_descriptorinformation are not always included at fixed locations, they may beincluded even when it is not necessary to do so, thereby avoidingwasting signaling resources. In particular, sincesignaling_on_internet_descriptor information may be included at at leastone of the service level or FIT level, it gives an advantageous effectthat broadband communication may be applied in a flexible mannerdepending on the needs of the transmitter-side.

FIG. 90 illustrates descriptors for the respective levels according toan embodiment of the present invention.

In FIG. 90, the FIT may include signaling information in the form oflevel-specific descriptor. Descriptors transmitted in group may bemanaged as illustrated in FIG. 90. Through version management based ongroup IDs, a receiver may manage descriptor information included whenthe FIT is received.

In FIG. 90, information managed by descriptors includesservice_status_descriptor, service_name_descriptor,capability_descriptor, service_bootstrap_descriptor,signaling_template_descriptor, and signaling_over_internet_descriptor.Description about each descriptor is replaced with the detaileddescription given above.

In the embodiment of FIG. 90, service_status_descriptor andservice_name_descriptor may be managed on the basis of group ID1.service_status_descriptor, service_name_descriptor,capability_descriptor, and service_bootstrap_descriptor may be managedon the basis of group ID2. And service_status_descriptor,service_name_descriptor, capability_descriptor,service_bootstrap_descriptor, signaling_template_descriptor, andsignaling_on_internet_descriptor may be managed on the basis of groupID3. In this document, signaling_on_internet_descriptor may be calledsignaling_on_inet descriptor. Also, signaling_bootstrap_descriptor maybe called signaling_broadcast_descriptor.

FIG. 91 illustrates an FIT to which level descriptors are appliedaccording to an embodiment of the present invention.

In FIG. 91, descriptions about the information included in the FIT arereplaced with the detailed descriptions given above.

In the FIT of FIG. 91, as described with reference to FIG. 90,service_status_descriptor, service_name_descriptor,capability_descriptor, service_bootstrap_descriptor,signaling_template_descriptor, and signaling_over_internet_descriptormay be included in the FIT as service level descriptors. A service leveldescriptor may be included selectively/optionally depending on theneeds.

In the embodiment of FIG. 91, information of signaling_on_internetdescriptor (signaling_on_inet_desc), signaling_bootstrap_descriptor(signaling_broadcast_desc), capability_descriptor (capability desc), andsignaling_template_descriptor (templete desc) may be included in the FITat the service level.

In what follows, a method for supporting service acquisition inassociation with a broadcast signaling service and an ESG service willbe described.

FIG. 92 illustrates a method for signaling a service ID according to anembodiment of the present invention.

The service ID information included in the FIT is unique not only withina broadcast stream but also within a broadcast area and may be signaledin 16 bits. The global service ID information included in an ESG servicefragment (@globalServiceID) and the service ID information included in aUSD element (@serviceID) are both URIs, both of which are globallyunique and represent the same service. In an embodiment, service IDinformation of the URI format included in a USD element may be called aglobal service ID.

The purpose of the service ID of the FIT is to provide a linkage for theannouncement structure and three service signaling in a broadcaststream. Therefore, maintaining uniqueness of the service ID within abroadcast stream is important.

The ESG and service layer signaling information (USD) may includeservice ID information of the URI format, and the FIT may includeservice ID information in 16 bits. Therefore, in order for a receiver tomatch a service of the ESG to a service of the broadcast signaling, itis preferable that at least one signaling data out of three signalingdata includes 16-bit service ID information and URI service IDinformation. The three signaling data are ESG, SLS information (USD),and FIT.

Therefore, in the embodiment of the present invention, SLS informationsuch as USD may include not only the service ID information of the URIformat (@ServiceID) but also the 16-bit service ID information(@atscServiceID). Therefore, by referring to the USD, a broadcastreceiver may map the service ID information of the FIT to the service IDinformation (@globalService) of a service fragment of the ESG.

In addition, the service ID information (FITServiceID) of the FIT may beincluded in the ESG. In this case, a broadcast receiver may match theservice ID information of the FIT immediately to the service IDinformation of the ESG.

FIG. 93 illustrates an embodiment of an ESG service fragment includingservice ID information of an FIT.

The 16-bit service ID information of the FIT is indicated byFITServcieID in FIG. 93. As a method for including FITServiceIDinformation in an ESG service fragment, three embodiments may beproposed as shown in FIG. 93.

1) FITServiceID information may be added as an attribute of a servicefragment.

2) FITServcieID information may be added as a child element of a servicefragment.

3) FITServiceID information may be added as a child element in thePrivate Extension part of a service fragment.

FIG. 94 illustrates a broadcast system structure according to anembodiment of the present invention.

In the ESG area, a service (TV-Channel) may be identified by a globalservice ID. In the FIT included in a broadcast stream, a service may beidentified by a service ID. A link between the global service ID of theESG and the service ID of the FIT may be performed through servicesignaling (USD). A broadcast receiver may link the service ID of the FITto the global service ID of the ESG by using the service ID and theglobal service ID of the USD.

However, as shown in FIG. 93, if the ESG includes the service ID of theFIT, a broadcast receiver may map the global service ID of the ESGdirectly to the service ID of the FIT. Therefore, even before SLSinformation such as USD is parsed, a receiver may match the servicesincluded in both data to each other directly by using the ESG and FITonly.

FIG. 95 illustrates a method for transmitting a broadcast signalaccording to an embodiment of the present invention.

A broadcast transmitter transmits a broadcast signal including a contentcomponent of a broadcast service, and a method for transmitting abroadcast signal according to an embodiment of the present invention isdescribed below.

A broadcast transmitter may process at least one of a broadcast serviceor a content component of the broadcast service according to a deliveryprotocol. The delivery protocol may include the ROUTE protocol or MMTprotocol.

A broadcast transmitter may generate service layer signaling (SLS)information S95010. The service layer signaling information includesinformation about discovery and acquisition of a broadcast service and acontent component of the broadcast service. Service layer signalinginformation is referred to as SLS in this document, detailed descriptionof which is substituted for by the description already given above.

The broadcast transmitter may generate service list information S95020.The service list information may include information for building abasic service list and discovering service layer signaling information.The service list information is referred to as the terms of FIT, FIC,LLS, and LCT, detailed description of which is substituted for by thedescription already given above.

The broadcast transmitter may perform physical layer processing on theservice list information, service layer signaling information, andcontent component. The broadcast transmitter may perform physical layerprocessing on the service list information, service layer signalinginformation, and content component; generate a signal frame; andtransmit the generated signal frame. Physical layer processing of thebroadcast transmitter is described with reference to FIGS. 18 to 40.

A content component and service layer signaling information may betransmitted by using at least one delivery protocols between the ROUTEand the MMT protocols.

The service list information may include signaling information at theservice list information level and signaling information at the servicelevel. The signaling information at the service list information levelmay include signaling information about all of the services described bythe service list information. The signaling information at the servicelevel may include signaling information about a specific serviceincluded in the service list information.

The signaling information at the service list information level mayinclude capability information, broadcast signaling locationinformation, and URL signaling information. The capability informationmay indicate the capability required for processing of a broadcastservice. The broadcast signaling location information may includeaddress information required for obtaining service layer signalinginformation. URL signaling information may indicate a URL at which anESG or a service layer signaling file about all of the services includedin the service list information may be obtained. The signalinginformation at the service layer signaling information level mayindicate a URL at which an ESG or service layer signaling file about thecorresponding service may be obtained.

The capability information, broadcast signaling location information,and URL signaling information at the service list information level; andthe URL signaling information at the service layer signaling informationlevel may be included in the service list informationselectively/optionally.

The service list information may include service ID information of16-bit integer format for identifying a broadcast service, and theservice layer signaling information may include the service IDinformation of 16-bit integer format and global service ID informationof URI format. The global service ID information may be included in theESG transmitted over broadband.

The service layer signaling information may be stored as a signalingtemplate. A signaling template may be pre-shared between a broadcasttransmitter and a broadcast receiver. When a signaling instance whichchanges service signaling information is generated, a broadcasttransmitter may compare the signaling instance with a signaling templateand transmit the difference as Diff information.

FIG. 96 illustrates a broadcast signal transmitter and a broadcastsignal receiver according to an embodiment of the present invention.

The broadcast signal transmitter 96100 comprises a broadcast contentencoder 96110, signaling processor 96120, and physical layer processor96130. FIG. 95 and the detailed descriptions given above are applied tothe operation of the broadcast signal transmitter.

The broadcast content encoder 96110 may process broadcast data accordingto a delivery protocol. The broadcast data may be encoded/formattedaccording to the ROUTE or MMT protocol. The broadcast data maycorrespond to a content component.

The signaling processor 96120 may generate signaling information. Thesignaling information may include service list information and servicelayer signaling information. The description about the present inventiongiven in detail above may be applied to the description of the servicelist information and service layer signaling information.

The physical layer processor 96130 may perform physical layer processingon the broadcast data processed by the broadcast content processor 96110and signaling information generated by the signaling processor 96120.The physical layer processor 96130 may transmit a physical layerprocessed signal frame, where the operation of the physical layerprocessor 96130 may be described by the descriptions given withreference to FIGS. 18 to 40.

A broadcast signal receiver 96200 may comprise a broadcast contentdecoder 96210, signaling parser 96220, and physical layer parser 96230.

The physical layer parser 96230 may perform physical layer processing ona receiver broadcast signal frame and extract broadcast data andsignaling information.

The signaling parser 96220 may parse signaling information and obtainservice list information and service layer signaling information. Thebroadcast content decoder 96210 may process a content componentcorresponding to a service according to a delivery protocol. Thebroadcast data may be decoded according to the ROUTE or MMT protocol.

The broadcast receiver 96200 may control the physical layer parser 96230according to the signaling information obtained by the signaling parser96220 and extract data corresponding to a specific service from a signalframe. And the broadcast receiver 96200 may process the extracted databy using the broadcast content decoder 96210 and output/provide aservice/service content.

A module or unit may comprise processors executing sequential operationsteps stored in the memory (or storage unit). The individual stepsdescribed in the embodiments above may be performed byhardware/processors. Each individual module/block/unit described in theembodiment above may be operated as hardware/processor. Also, themethods proposed by the present invention may be executed as programcodes. These codes may be written to a processor-readable storage mediumand therefore may be read by a processor provided by an apparatus.

Although the present invention has been described with reference toindividual drawings for the convenience of description, it is stillpossible to design so that embodiments described with reference to eachdrawing may be combined to implement a new embodiment. Also, dependingon the needs of those skilled in the art, designing a computer-readablerecording medium in which programs for executing the embodimentsdescribed above are stored also belongs to the technical scope of thepresent invention.

The apparatus and method according to the present invention are notlimited to the embodiments described above, but the entire or part ofthe embodiments may be combined selectively so that variousmodifications may be made to the embodiments.

Meanwhile, the method according to the present invention may beimplemented in the form of processor-readable program codes in arecording medium that may be read by a processor installed in a networkdevice. The processor-readable recording medium includes all kinds ofrecording devices storing data that may be read by the processor.Examples of processor-readable recording media include ROM, RAM, CD-ROM,magnetic tape, floppy disk, optical data storage device, andimplementation in the form of carrier waves such as transmission throughthe Internet. Also, the processor-readable recording medium may bedistributed over computer systems connected to each other through anetwork so that processor-readable codes may be stored and executed in adistributed manner.

Throughout the document, preferred embodiments of the present inventionhave been described with reference to appended drawings; however, thepresent invention is not limited to the embodiments above. Rather, itshould be noted that various modifications of the present invention maybe made by those skilled in the art to which the present inventionbelongs without leaving the technical scope of the present inventiondefined by the appended claims, and these modifications should not beunderstood individually from the technical principles or aspects of thepresent invention.

The present document describes both of the product invention and theprocess invention, and depending on the needs, descriptions of therespective inventions may be applied in a supplementary manner.

It should be understood by those skilled in the art that variousmodifications and variations of the present invention may be madewithout departing from the technical principles and scope. Therefore, itshould be understood that the present invention includes modificationsand variations thereof provided by the appended claims of the presentinvention and within their equivalent scope. The present documentdescribes both of an apparatus and a method according to the presentinvention, and descriptions of both of the apparatus and methodaccording to the present invention may be applied in a complementarymanner.

MODE FOR INVENTION

Various embodiments have been described in their best mode to embody thepresent invention

INDUSTRIAL APPLICABILITY

The present invention is used in a series of broadcast signal providingfields.

It should be understood by those skilled in the art that variousmodifications and variations of the present invention may be madewithout departing from the technical principles and scope. Therefore, itshould be understood that the present invention includes modificationsand variations thereof provided by the appended claims of the presentinvention and within their equivalent scope.

1-14. (canceled)
 15. A method for transmitting a broadcast signal, themethod comprising: generating Diff information by comparing an XMLtemplate and an XML signaling instance of service layer signalinginformation for one or more services of the broadcast signal, the Diffinformation represents a difference between the XML template and the XMLsignaling instance, the XML template is pre-shared between atransmission system and a reception system through HTTP(S) over thebroadband, the Diff information is encapsulated in metadataEnvelope; andtransmitting the broadcast signal carrying one or more componentsdelivered via a ROUTE (Real-Time Object Delivery over UnidirectionalTransport) protocol and service list information for the one or moreservices, wherein the service list information includes: first URL(Uniform Resource Locator) signaling information indicating a URL foracquiring a first ESG (Electronic Service Guide) or a service layersignaling file for all services when the first ESG or the first servicelayer signaling file is available via a broadband, the first URLsignaling information is used for Diff information transmitted via thebroadband, the service list information includes information for aservice identified by a service ID, the information for the serviceidentified by the service ID includes: capability information indicatingcapability required for processing of the service, broadcast signalinglocation information including address information required foracquiring service layer signaling information for the service, andsecond URL signaling information indicating a URL for acquiring a secondESG or a second service layer signaling file for the service when thesecond ESG or the second service layer signaling file is available viathe broadband.
 16. The method of claim 15, wherein the broadcast signalcarries one or more components delivered via are transmitted by using aMMT (MPEG Media Transport) protocol.
 17. The method of claim 15, whereinthe metadataEnvelope includes: an XML signaling instance ID foridentifying the XML signaling instance and an XML template ID foridentifying the XML template.
 18. The method of claim 15, wherein thebase URL is used to make a request for the Diff information transmittedvia the broadband.
 19. The method of claim 18, wherein the second URLsignaling information is used for Diff information for the serviceidentified by the service ID.
 20. A device for transmitting a broadcastsignal, the device comprising: a Diff generator configured to generateDiff information by comparing an XML template and an XML signalinginstance of service layer signaling information for one or more servicesof the broadcast signal, the Diff information represents a differencebetween the XML template and the XML signaling instance, the XMLtemplate is pre-shared between a transmission system and a receptionsystem through HTTP(S) over the broadband, the Diff information isencapsulated in metadataEnvelope; and a transmitter configured totransmit the broadcast signal carrying one or more components deliveredvia a ROUTE (Real-Time Object Delivery over Unidirectional Transport)protocol and service list information for the one or more services,wherein the service list information includes: first URL (UniformResource Locator) signaling information indicating a URL for acquiring afirst ESG (Electronic Service Guide) or a service layer signaling filefor all services when the first ESG or the first service layer signalingfile is available via a broadband, the first URL signaling informationis used for Diff information transmitted via the broadband, the servicelist information includes information for a service identified by aservice ID, the information for the service identified by the service IDincludes: capability information indicating capability required forprocessing of the service, broadcast signaling location informationincluding address information required for acquiring service layersignaling information for the service, and second URL signalinginformation indicating a URL for acquiring a second ESG or a secondservice layer signaling file for the service when the second ESG or thesecond service layer signaling file is available via the broadband. 21.The device of claim 20, wherein the broadcast signal carries one or morecomponents delivered via an MMT (MPEG Media Transport) protocol.
 22. Thedevice of claim 20, wherein the metadataEnvelope includes: an XMLsignaling instance ID for identifying the XML signaling instance and anXML template ID for identifying the XML template.
 23. The device ofclaim 20, wherein the base URL is used to make a request for the Diffinformation.
 24. The device of claim 23, wherein the second URLsignaling information is used for Diff information for the serviceidentified by the service ID.
 25. A method for receiving a broadcastsignal, the method comprising: receiving the broadcast signal carryingone or more components delivered via a ROUTE (Real-Time Object Deliveryover Unidirectional Transport) protocol and service list information forthe one or more services, wherein the service list information includes:first URL (Uniform Resource Locator) signaling information indicating aURL for acquiring a first ESG (Electronic Service Guide) or a servicelayer signaling file for all services when the first ESG or the firstservice layer signaling file is available via a broadband, the servicelist information includes information for a service identified by aservice ID, the information for the service identified by the service IDincludes: capability information indicating capability required forprocessing of the service, broadcast signaling location informationincluding address information required for acquiring service layersignaling information for the service, and second URL signalinginformation indicating a URL for acquiring a second ESG or a secondservice layer signaling file for the service when the second ESG or thesecond service layer signaling file is available via the broadband; andrecovering an XML signaling instance of the service layer signalinginformation for one or more services of the broadcast signal by applyingDiff information on an XML template, wherein: the Diff information isgenerated by comparing the XML template and the XML signaling instance,the Diff information represents a difference between the XML templateand the XML signaling instance, the XML template is pre-shared between atransmission system and a reception system through HTTP(S) over thebroadband, the Diff information is encapsulated in metadataEnvelope, thefirst URL signaling information is used for Diff information transmittedvia the broadband.
 26. The method of claim 25, wherein the broadcastsignal carries one or more components delivered via are transmitted byusing a MMT (MPEG Media Transport) protocol.
 27. The method of claim 25,wherein the metadataEnvelope includes: an XML signaling instance ID foridentifying the XML signaling instance and an XML template ID foridentifying the XML template.
 28. The method of claim 25, wherein thebase URL is used to make a request for the Diff information transmittedvia the broadband.
 29. The method of claim 28, wherein the second URLsignaling information is used for Diff information for the serviceidentified by the service ID.
 30. A device for receiving a broadcastsignal, the device comprising: a receiver configured to receive thebroadcast signal carrying one or more components delivered via a ROUTE(Real-Time Object Delivery over Unidirectional Transport) protocol andservice list information for the one or more services, wherein theservice list information includes: first URL (Uniform Resource Locator)signaling information indicating a URL for acquiring a first ESG(Electronic Service Guide) or a service layer signaling file for allservices when the first ESG or the first service layer signaling file isavailable via a broadband, the service list information includesinformation for a service identified by a service ID, the informationfor the service identified by the service ID includes: capabilityinformation indicating capability required for processing of theservice, broadcast signaling location information including addressinformation required for acquiring service layer signaling informationfor the service, and second URL signaling information indicating a URLfor acquiring a second ESG or a second service layer signaling file forthe service when the second ESG or the second service layer signalingfile is available via the broadband; and a Diff applier configured torecover an XML signaling instance of the service layer signalinginformation for one or more services of the broadcast signal by applyingDiff information on an XML template, wherein: the Diff information isgenerated by comparing the XML template and the XML signaling instance,the Diff information represents a difference between the XML templateand the XML signaling instance, the XML template is pre-shared between atransmission system and a reception system through HTTP(S) over thebroadband, the Diff information is encapsulated in metadataEnvelope, thefirst URL signaling information is used for Diff information transmittedvia the broadband.
 31. The device of claim 30, wherein the broadcastsignal carries one or more components delivered via are transmitted byusing a MMT (MPEG Media Transport) protocol.
 32. The device of claim 30,wherein the metadataEnvelope includes: an XML signaling instance ID foridentifying the XML signaling instance and an XML template ID foridentifying the XML template.
 33. The device of claim 30, wherein thebase URL is used to make a request for the Diff information transmittedvia the broadband.
 34. The device of claim 33, wherein the second URLsignaling information is used for Diff information for the serviceidentified by the service ID.